![]() I have read many of the discussions from people experiencing similar problems. Long story short - yesterday, I tried everything from re-installing the Nginx-ingress and cert-manager to starting a new Azure Kubernetes Service from scratch, but every time I end up in the same situation. However, we noticed later on that the ingress controller actually serves two certificates (one of which has a common name: "Kubernetes Ingress Controller Fake Certificate" and an Alternative name: "ingress.local"): The browser can validate the Let's Encrypt certificate. When visiting our page in a web-browser, we notice nothing out of the ordinary at first - HTTPS was working fine. I followed the basic setup advice from the Microsoft documentation: ![]() I'm using the " NGINX Ingress Controller" and " cert-manager" for routing and certificate generation (through Let's Encrypt). We are running a AKS Kubernetes cluster on Azure.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |