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 Aug 19, 2020. It is now read-only.
The helm chart does not have a liveness or readiness probe for the loadbalancer-keepalived container. We've had cases where kube-keepalived-vip logs would show everything fine with one in master state and others in backup, but there were no VIPs created on any network interfaces. kube-keepalived-vip should expose a /health endpoint for use in probes. Additionally, that health endpoint should interrogate the status of the VIPs and only respond successfully (200) if the VIPs exist on the interface.
The text was updated successfully, but these errors were encountered:
The helm chart does not have a liveness or readiness probe for the loadbalancer-keepalived container. We've had cases where kube-keepalived-vip logs would show everything fine with one in master state and others in backup, but there were no VIPs created on any network interfaces. kube-keepalived-vip should expose a /health endpoint for use in probes. Additionally, that health endpoint should interrogate the status of the VIPs and only respond successfully (200) if the VIPs exist on the interface.
The text was updated successfully, but these errors were encountered: