aks 1.24 ingress not exposed

owen.kim 176 Reputation points
2022-09-15T07:52:49.423+00:00

As soon as you upgrade from aks 1.2x version to 1.24, you will not be able to access the ingress through the controller.

In other words, I can't connect to the pod.
Is there any way to check this?
It worked fine in 1.23, but I can't connect as soon as I upgrade to 1.24.

With port-forward, the host connects to the pod.

241329-aks.png

Azure Kubernetes Service
Azure Kubernetes Service
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
2,462 questions
{count} votes

Accepted answer
  1. srbhatta-MSFT 8,586 Reputation points Microsoft Employee
    2022-09-19T05:41:11.79+00:00

    Hi @owen.kim ,
    Thanks for reaching out to Microsoft QnA.
    Can you check the load balancer health probe configuration corresponding to nginx-ingress-controller service IP. If the health probe is configured with protocol “HTTP” and path “/” the nginx-ingress-controller service will most likely fail the load balancer probes.
    Check the nginx ingress controller service describe output. If the "service.beta.kubernetes.io/azure-load-balancer-health-probe-request-path=/healthz" annotation is missing the LB health probes will possibly fail.
    Could you please update the nginx-ingress-controller service to use the annotation "service.beta.kubernetes.io/azure-load-balancer-health-probe-request-path=/healthz" which will set the correct path of /healthz . That should make the health probes work as expected. If this doesn't help, please reach back and I would check into this further.
    Thanks :)

    ----------

    Please don't forget to Accept as answer and Upvote if you think the information provided was useful so that it can help others in the community looking for help on similar issues.

    7 people found this answer helpful.

5 additional answers

Sort by: Most helpful
  1. Igor Rocha 0 Reputation points
    2023-01-25T19:55:42.66+00:00

    Hello guys,

    The issue is related to the readinessProbe used inside the nginx on the 1.24 version

    So you really need to edit your load balancer service if you already has it deployed, or when will install it use this annotation

    service.beta.kubernetes.io/azure-load-balancer-health-probe-request-path: /healthz

             readinessProbe:
                failureThreshold: 3
                httpGet:
                  path: /healthz
                  port: 10254
                  scheme: HTTP
    
    
    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.