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
{{ message }}
This repository has been archived by the owner on Feb 24, 2024. It is now read-only.
A Service exposed through an Ingress must respond to health checks from the load balancer. Any container that is the final destination of load-balanced traffic must do one of the following to indicate that it is healthy:
Serve a response with an HTTP 200 status to GET requests on the / path.
Configure an HTTP readiness probe. Serve a response with an HTTP 200 status to GET requests on the path specified by the readiness probe. The Service exposed through an Ingress must point to the same container port on which the readiness probe is enabled.
Since the load balancer does not have the webhook secret all response are either 401 or 404s. Can a health check endpoint be added which returns a 200 response.
The text was updated successfully, but these errors were encountered:
GKE ingress configures a load balancer with a health check to the flux-recv port. The requirements for the health check are that a 200 response is returned: https://cloud.google.com/kubernetes-engine/docs/concepts/ingress#health_checks
Since the load balancer does not have the webhook secret all response are either 401 or 404s. Can a health check endpoint be added which returns a 200 response.
The text was updated successfully, but these errors were encountered: