This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 27%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPR%3C/text%3E%3C/svg%3E)
I have upgraded the aks version to 1.24.9, it has been upgraded successfully . Now ingress is not working. At configuration level everything looks good. Even added the annotation /heaalthz into ingress config, but no luck.
Getting below logs, badly stuck :-
NGINX Ingress controller Release: v1.2.1 Build: xxxxxxx Repository: https://github.com/kubernetes/ingress-nginx nginx version: nginx/1.19.10
W0330 17:43:21.755583 7 client_config.go:617] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work. I0330 17:43:21.755715 7 main.go:230] "Creating API client" host="https://x.0.x.x:x" I0330 17:43:21.783132 7 main.go:274] "Running in Kubernetes cluster" major="1" minor="24" git="v1.24.9" state="clean" commit="xxxxxxxxx" platform="linux/amd64" I0330 17:43:22.210872 7 main.go:104] "SSL fake certificate created" file="/etc/ingress-controller/ssl/default-fake-certificate.pem" I0330 17:43:22.232701 7 ssl.go:531] "loading tls certificate" path="/usr/local/certificates/cert" key="/usr/local/certificates/key" I0330 17:43:22.257160 7 nginx.go:256] "Starting NGINX Ingress controller" I0330 17:43:22.270906 7 event.go:285] Event(v1.ObjectReference{Kind:"ConfigMap", Namespace:"stage", Name:"new-ingress-ingress-nginx-controller", UID:"xxxxxx", APIVersion:"v1", ResourceVersion:"266020028", FieldPath:""}): type: 'Normal' reason: 'CREATE' ConfigMap stage/new-ingress-ingress-nginx-controller I0330 17:43:23.365442 7 store.go:429] "Found valid IngressClass" ingress="stage/new-ingress" ingressclass="nginx" I0330 17:43:23.366045 7 event.go:285] Event(v1.ObjectReference{Kind:"Ingress", Namespace:"stage", Name:"new-ingress", UID:"xxxxxxxx", APIVersion:"networking.k8s.io/v1", ResourceVersion:"266049461", FieldPath:""}): type: 'Normal' reason: 'Sync' Scheduled for sync I0330 17:43:23.366138 7 backend_ssl.go:65] "Adding secret to local store" name="stage/unificonnect-tls-cert" I0330 17:43:23.460119 7 nginx.go:299] "Starting NGINX process" I0330 17:43:23.460597 7 leaderelection.go:248] attempting to acquire leader lease stage/ingress-controller-leader... I0330 17:43:23.460999 7 nginx.go:319] "Starting validation webhook" address=":8443" certPath="/usr/local/certificates/cert" keyPath="/usr/local/certificates/key" I0330 17:43:23.461416 7 controller.go:167] "Configuration changes detected, backend reload required" I0330 17:43:23.467469 7 status.go:84] "New leader elected" identity="new-ingress-ingress-nginx-controller-xxxx-s6j86" I0330 17:43:23.546688 7 controller.go:184] "Backend successfully reloaded" I0330 17:43:23.547005 7 controller.go:195] "Initial sync, sleeping for 1 second" I0330 17:43:23.547422 7 event.go:285] Event(v1.ObjectReference{Kind:"Pod", Namespace:"stage", Name:"new-ingress-ingress-nginx-controller-xxxx-pfgfn", UID:"151e7520-4fe2-4c63-b444-3519e3e28654", APIVersion:"v1", ResourceVersion:"266049782", FieldPath:""}): type: 'Normal' reason: 'RELOAD' NGINX reload triggered due to a change in configuration I0330 17:44:10.687489 7 status.go:84] "New leader elected" identity="new-ingress-ingress-nginx-controller-xxxxxx-cq6lw"
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 30%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAB%3C/text%3E%3C/svg%3E)
Hello Patwa, Rahul
I can see you are using NGINX Ingress controller Release: v1.2.1
As per https://github.com/kubernetes/ingress-nginx#supported-versions-table, v1.2.1 is compatible with Kubernetes versions 1.23, 1.22, 1.21, 1.20, 1.19.
I hope this is helpful. If any clarification needed, let me know and I will do my best to answer.
Please "Accept as Answer" and Upvote if it helped, so that it can help others in the community looking for help on similar topics.
Thank you!
still no luck post upgrade of nginx ingress as well. still at same page.
-------------------------------------------------------------------------------
NGINX Ingress controller
Release: v1.7.0
Build: 7xxxxxxx
Repository: https://github.com/kubernetes/ingress-nginx
nginx version: nginx/1.21.6
-------------------------------------------------------------------------------
W0330 19:44:05.484770 8 client_config.go:618] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
I0330 19:44:05.484957 8 main.go:209] "Creating API client" host="https://10.0.x.x"
I0330 19:44:05.512557 8 main.go:253] "Running in Kubernetes cluster" major="1" minor="24" git="v1.24.9" state="clean" commit="xxxxx" platform="linux/amd64"
I0330 19:44:06.228699 8 main.go:104] "SSL fake certificate created" file="/etc/ingress-controller/ssl/default-fake-certificate.pem"
I0330 19:44:06.262502 8 ssl.go:533] "loading tls certificate" path="/usr/local/certificates/cert" key="/usr/local/certificates/key"
I0330 19:44:06.275590 8 nginx.go:261] "Starting NGINX Ingress controller"
I0330 19:44:06.292838 8 event.go:285] Event(v1.ObjectReference{Kind:"ConfigMap", Namespace:"stage", Name:"new-ingress-ingress-nginx-controller", UID:"xxx-c9ab-4a12-a221-xx", APIVersion:"v1", ResourceVersion:"266079269", FieldPath:""}): type: 'Normal' reason: 'CREATE' ConfigMap stage/new-ingress-ingress-nginx-controller