-
Notifications
You must be signed in to change notification settings - Fork 75
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
enable outlier detection #276
Comments
Might not work as we are using Serverless NEGs that don't have health checks. |
Outlier detection doesn't rely on (active) healthchecks, it's basically acting on observed response codes to normal requests. It is available for serverless NEGs for a while now, with some limitations (I forget which but IIRC one of the config options wasn't applicable). |
It might not have solved this particular outage though, if nothing else since it's an LB behavior and LBs are impacted in some way (haven't had a chance to look further for now). |
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 |
/remove-lifecycle stale We should still probably do this, it's just hard to prioritize versus getting the rest of the infra migrated into the community, we're rarely having outages as-is and it's not 100% clear if this would solve the problem(s) (needs more investigating, just haven't really had time and nobody else seems to have looked yet). |
We should enable https://cloud.google.com/load-balancing/docs/https/setting-up-global-traffic-mgmt#configure_outlier_detection
https://github.com/kubernetes/k8s.io/tree/main/infra/gcp/terraform/modules/oci-proxy
I think last time I looked into this I got hung up on migrating to current terraform / modules versions in k8s.io and then got interrupted with other priorities, but it might be possible to do without updating those first.
xref: #274 (comment), previously #234
The text was updated successfully, but these errors were encountered: