By kevg
I have an easily reproducible problem where I create a Kubernetes cluster, install the NGINX Ingress controller, create and expose a hello world app, create an ingress with a routing rule to that app, create an ingress, install cert-manager, and either an Issuer or ClusterIssuer creates the right certificate but the ingress doesn’t pick it up. Any ideas? The reproduction steps are detailed in https://github.com/jetstack/cert-manager/issues/4012
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Looking at the GitHub issue you linked, it seems the certificate was being created correctly but ingress-nginx just never reloaded it. As far as I can tell, that was a known behavior in some older ingress-nginx versions, where the controller kept serving its default self-signed cert even though cert-manager had already updated the Secret.
Based on the issue, the usual work around was to restart the ingress controller or setting a default SSL certificate in the ingress-nginx args. In the original thread, switching from a wildcard host to a specific host also made ingress-nginx start serving the right cert.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Start building today
From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.
