application-gateway-kubernetes-ingress
application-gateway-kubernetes-ingress copied to clipboard
Health Probe Interval pulls from Readiness Probe, not Liveness Prove
Describe the bug In the documentation, it says that AGIC will pull the settings from the Liveness Probe https://azure.github.io/application-gateway-kubernetes-ingress/annotations/#health-probe-interval
interval in liveliness probe definition is also used as a interval for health probe
In the code, it pulls from a readiness probe: https://github.com/Azure/application-gateway-kubernetes-ingress/blob/66403512db795c275c52dfe29d4a5d324dd15b1a/pkg/appgw/health_probes.go#L261
To Reproduce Steps to reproduce the behavior: Deploy a statefulset or deployment with readiness and liveness probes. Update the liveness probe, observe agic won't update. Update the readiness probe, observe the health check in apgw changing.
Ingress Controller details
- Output of
kubectl describe pod <ingress controller> . Thepod name can be obtained by running helm list. - Output of `kubectl logs
. - Any Azure support tickets associated with this issue.