You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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)
The text was updated successfully, but these errors were encountered: