This message was deleted.

I could see that the

values.yaml

file in the Helm folder had various fields related to ingress (ex ingressPath, ingressPathType, domainSuffix). However, these values were only used to define the configMap template, and the actual creation of the ingress appeared to be hidden by running the

/manager

command in the quay.io/bentoml/yatai-deployment:1.1.9 docker image. Is this something that can't be fixed with some modifications to the values.yaml file to meet my requirements?

@Xipeng Guan can you help out here?

Sorry, yatai does not support this feature, which defeats the original purpose of yatai: not to change bento's business logic, just to deploy bento on k8s, but its behavior is the same as if it were deployed locally So, you can implement this feature in the bento code

@Xipeng Guan Thank you for your answer, I understand the purpose of yatai. I'll think about implementing the API as a different path in the bento code, or using it like a wildcard record DNS to deploy multiple bentos utilizing the suffix hostname feature.