-
Notifications
You must be signed in to change notification settings - Fork 298
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to implement content-based health check for GKE ingress #2468
Comments
Is there another place where I can address this issues? It's rather urgent. |
/kind feature |
I would be willing to contribute on this one :) |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
I said, I am willing to contribute @k8s-ci-robot 🤣 |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
I want to implement a content-based health check for my GKE ingress. These kinds of health checks are usually specified in the BackendConfig CRD. My current BackendConfig looks like this:
As seen in the link above, Google DOES support content-based health checks. But I cannot see, how to configure this. I expected something like:
but I cannot find anything about it. Not even in the CRD source code. Did anyone ever do this successfully? How?
In the GCP console you can set it like this:
The text was updated successfully, but these errors were encountered: