Kube API unavailability results in a gloo container crash #8107
Labels
Area: Stability
Issues related to stability of the product, engineering, tech debt
Prioritized
Indicating issue prioritized to be worked on in RFE stream
Type: Bug
Something isn't working
Gloo Edge Version
1.13.x (latest stable)
Kubernetes Version
None
Describe the bug
A customer is facing regular kube-API outage (on all clouds AWS, Azure and GCP) and when it happens, gloo container is crashing on the gloo pod (because of the election not able to choose the lead).
If the API server is unavailable during a scale-out event (increase of load for instance), the new gateway-proxy won't have the configuration from gloo due to this election problem.
Steps to reproduce the bug
iptables -A INPUT -p tcp --dport 6443 -j DROP
)Expected Behavior
Gloo should be resilient to the API outage, at least not crashing.
Additional Context
One or more envoy instances are not connected to the control plane for the last 1 minute
┆Issue is synchronized with this Asana task by Unito
The text was updated successfully, but these errors were encountered: