AGIC adds pod to the backed pool even if it is not in ready state

[yarashagarwal]

Describe the bug A clear and concise description of what the bug is. If a pod is in running state but is not yet "ready" because of the container is still bringing itself up, AGIC still updates the pod IP address to the backend pool of the App Gateway

To Reproduce Steps to reproduce the behavior:

1. Create a Pod with a readiness probe set to 1 minute
2. As soon as the pod is running state, AGIC updates the backendpool
3. Observe the traffic flow into the new pod which is still not ready Expected behaviour should be that AGIC does not update the backend pools on the app gateway till the pods are in ready state

Ingress Controller details

• Output of kubectl describe pod <ingress controller> . The pod name can be obtained by running helm list. ingress-appgw-container: Container ID: containerd://0c7ea4a90fa1ca80e9f196c9e90a99dc003b297524d02d905d7b04726db33275 Image: mcr.microsoft.com/azure-application-gateway/kubernetes-ingress:1.5.3 Image ID: mcr.microsoft.com/azure-application-gateway/kubernetes-ingress@sha256:efd474df2c22af6e5abc201eb417098acec988feb70a763bb0782eda743fff42 Port: Host Port: State: Running
• Output of `kubectl logs .
• Any Azure support tickets associated with this issue.

[mtrin]

I'm not from Azure or MS but I had to figure this out. Basically following this doc should sort your issue https://azure.github.io/application-gateway-kubernetes-ingress/how-tos/minimize-downtime-during-deployments/

you need to give agic a bit of time to update