Skip to content
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

Add support to GKE's BackendConfig CRD #644

Open
retpolanne opened this issue Aug 25, 2020 · 0 comments
Open

Add support to GKE's BackendConfig CRD #644

retpolanne opened this issue Aug 25, 2020 · 0 comments

Comments

@retpolanne
Copy link
Contributor

Currently, a LB's healthcheck endpoint on GCP can be changed through readiness probes that can be defined via teresa.yaml. However, this is only applied when the app is being deployed for the first time. If you want to change the healthcheck endpoint later, you need to do it manually.

However, google has a BackendConfig CRD that allows you to change configurations from the LB stack from Kubernetes. You can change the healthcheck (https://cloud.google.com/kubernetes-engine/docs/concepts/ingress#direct_hc), backend service timeouts (https://cloud.google.com/kubernetes-engine/docs/how-to/ingress-features#timeout). It has to be associated to an ingress via annotation (https://cloud.google.com/kubernetes-engine/docs/how-to/ingress-features#associating_backendconfig_with_your_ingress)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant