Starting on release 1.8.2, Okteto comes with 2 ingress controllers, one for the okteto control plane, and one for the user’s applications. If you need to configure proxy protocol for your applications, you can expose the okteto-nginx ingress controller as a load balancer like this:
okteto-nginx:
controller:
service:
type: LoadBalancer
and create DNS entries for:
- *.subdomain → for the IP of
okteto-nginx - okteto.subdomain, buildkit.subdomain and regustry.subdomain → for the IP of
ingress-nginx
Also, you have to configure the same wildcard certificate in wildcardCertificate.name as the default certificate of okteto-nginx::
okteto-nginx:
controller:
extraArgs:
default-ssl-certificate: $(POD_NAMESPACE)/<<your-ssl-certificate-secret>>