Document "publicOverride"

[pchico83]

Document "publicOverride"

[rberrelleza]

I'd prefer if we don't ask the customer to create a separate ingress for this (since our ingress might change). is there a way for use to create the required ingress in the chart instead @pchico83 ?

[pchico83]

@rberrelleza for customers interested in this feature, they usually have their one ingress controller. We could support it for nginx, but I think it's better to explain how to do it and don't support it in our chart since this is an advanced scenario

[rberrelleza]

the ingress controller is decoupled from the ingress definition. As long as we allow them to set the class, we could create it the same way that we do for the okteto.SUBDOMAIN one. That ingress changes a lot, I don't think it's a good idea to tell our customers to create it. Let's brainstorm on what does it mean to support this before we document this.