I have set up an Azure Kubernetes Service (AKS) cluster and installed Nginx Ingress on it. I’m using a domain name from AWS Route 53 and created an A record pointing to the external IP of my Nginx Ingress Controller. Next, I installed Cert-Manager and Rancher on the AKS cluster, all deployed via Helm.
However, I’m encountering three issues:
- When I attempt to access my server, I receive a “404 Not Found” error.
- I also get a “Your Connection is Not Private” SSL error.
- When I view the certificate on the url that is ‘Kubernetes Ingress Controller Fake Certificate’
I’ve checked my Kubernetes cluster, and I can confirm that the issuer and certificate were created by Cert-Manager using Let’s Encrypt. Below are the steps I followed:
az aks create
–resource-group rancher-rg
–name rancher-server
–kubernetes-version
–node-count 3
–node-vm-size Standard_D2_v3
…
helm upgrade --install
ingress-nginx ingress-nginx/ingress-nginx
–namespace ingress-nginx
–set controller.service.type=LoadBalancer
–set controller.service.annotations.“service.beta.kubernetes.io/azure-load-balancer-health-probe-request-path”=/healthz
–set controller.service.externalTrafficPolicy=Local
–version 4.8.0
–create-namespace
…
helm install cert-manager jetstack/cert-manager
–namespace cert-manager
–create-namespace
–set installCRDs=true
…
helm install rancher rancher-latest/rancher
–namespace cattle-system
–set hostname=rancher-mydomain.com
–set bootstrapPassword=admin
–set ingress.tls.source=letsEncrypt
–set letsEncrypt.email=mygmail@gmail.com
–set letsEncrypt.ingress.class=nginx
…
I’d appreciate guidance on resolving the 404 error and SSL issues to make my setup fully functional. Thank you!
