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
The GCE loadbalancer perfoms health checks to see if backend are fit to take traffic. These health checks seem to be derived from the readinessProbe defined in the pod the service is pointing to where the service is taken from the ingress.
However, a pod can expose multiple ports where each port can be exposed by a service, but there can be only one readinessProbe on a pod. Also the semantics of each exposed service doe not have to match the semantics of the readinessProbe.
It would make more sense if the LB-healthcheck would be defined either in the ingress or in the service.
The text was updated successfully, but these errors were encountered:
The GCE loadbalancer perfoms health checks to see if backend are fit to take traffic. These health checks seem to be derived from the readinessProbe defined in the pod the service is pointing to where the service is taken from the ingress.
However, a pod can expose multiple ports where each port can be exposed by a service, but there can be only one readinessProbe on a pod. Also the semantics of each exposed service doe not have to match the semantics of the readinessProbe.
It would make more sense if the LB-healthcheck would be defined either in the ingress or in the service.
The text was updated successfully, but these errors were encountered: