Skip to main content
Version: 1.48

Setting up certificates with cert-manager and Let's Encrypt

cert-manager automates certificate requests from Let's Encrypt, a free and automated Certificate Authority.

Okteto requires a wildcard certificate, so you must use a DNS01 auth method in your Issuer. The list of supported DNS01 providers has the compatible options.

The Okteto community maintains guides on using cert-manager with different cloud providers:

Configure Okteto to use your certificate​

Create your Certificate resource in the namespace where Okteto is installed. After cert-manager issues it, cert-manager stores the certificate in the secret set in the Certificate's spec.secretName. Add the following to your Helm configuration file, replacing your-ssl-certificate-secret with that name, to tell Okteto and NGINX to use your certificate:

config.yaml
wildcardCertificate:
create: false
name: your-ssl-certificate-secret

ingress-nginx:
controller:
extraArgs:
default-ssl-certificate: $(POD_NAMESPACE)/your-ssl-certificate-secret
warning

Both settings are required. wildcardCertificate.create: false stops Okteto from generating its self-signed certificate, which also removes the secret that default-ssl-certificate points at. If you don't update that argument as well, the ingress controller falls back to its own built-in fake certificate. This fails quietly: cert-manager reports your certificate as Ready, and the hosts Okteto creates ingresses for still serve it over SNI, but any request that doesn't match one of those hosts shows a certificate warning.

Upgrade your Okteto installation to apply the new configuration.