aks 1.24 ingress not exposed

Question

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.

Answer 1

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.

Answer 2

I found out that it only works with local traffic policy. May it help someone.

   service:  
     externalTrafficPolicy: Local  
     annotations:  
       service.beta.kubernetes.io/azure-load-balancer-internal: "true"  
       service.beta.kubernetes.io/azure-load-balancer-health-probe-request-path: /healthz  

Answer 3

apiVersion: apps/v1  
kind: Deployment  
metadata:  
  name: mario  
  labels:  
    app: mario  
spec:  
  replicas: 1  
  selector:  
    matchLabels:  
      app: mario  
  template:  
    metadata:  
      labels:  
        app: mario  
    spec:  
      containers:  
      - name: mario  
        image: pengbai/docker-supermario  
---  
apiVersion: v1  
kind: Service  
metadata:  
   name: mario  
spec:  
  selector:  
    app: mario  
  ports:  
  - port: 80  
    protocol: TCP  
    targetPort: 8080  
  type: ClusterIP  
---  
  
apiVersion: networking.k8s.io/v1  
kind: Ingress  
metadata:  
  name: mario    
spec:  
  ingressClassName: nginx  
  rules:  
  - host: mario.test.com  
    http:  
      paths:  
      - path: /  
        pathType: Prefix  
        backend:  
          service:   
            name: mario  
            port:  
              number: 80  
  tls:  
  - hosts:  
    - mario.test.com  
    secretName: aks-ingress-tls  

sample yaml

Answer 4

Thanks! solution still working.... at nov 2022 for kubernetes 1.24.6.

Answer 5

This isn't doing it for me, using internal load balancer. I have these annotations:

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

Any idea @srbhatta-MSFT ?