Please describe your use case / problem.
I'm trying to use ambassador with network endpoint groups in GKE. The relevant documentation states:
For relevant Pods, the corresponding Ingress controller manages a readiness gate of type cloud.google.com/load-balancer-neg-ready. The Ingress controller polls the load balancer's health check status, which includes the health of all endpoints in the NEG. When the load balancer's health check status indicates that the endpoint corresponding to a particular Pod is healthy, the Ingress controller sets the Pod's readiness gate value to True. The kubelet running on each Node then computes the Pod's effective readiness, considering both the value of this readiness gate and, if defined, the Pod's readiness probe.
The first step in the NEG healthcheck is to hit the / route on the service port of the pod and see if it returns a HTTP 200. However, this isn't how ambassador pods behave by default.
Describe the solution you'd like
Please provide a way to configure 200 OK to be returned at /, or for the healthcheck route to be configurable
Describe alternatives you've considered
Can't think of anything. Using GKE, the backend controllers override any manual changes to the healthchecks and don't provide a way of configuring it via annotations. I have raised this issue with GCP.
Additional context
Add any other context about the feature request here.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
/reopen
@pratikmallya looks like stale bot does not support reopening? Maybe we should make a new issue?
FYI you could probably set up a similar workaround that works for istio:
Also, support for configuring google's health checks from k8s is supposedly coming.
This is an issue that prevents this guide from working when used with the helm chart Edge install.
The probe routes do not appear to be configurable.
Most helpful comment
/reopen