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 Jul 30, 2021. It is now read-only.
With self hosted etcd we see that significant memory pressure on the masters will cause the cluster to become unstable.
This will mean that the kubelet will eventually mark all the etcd pods unhealthy and thus the kube-proxy will rejecting packets headed for the kube-system/etcd-service:client
At this point the apiserver is unable to start as it is configured to connect to etcd cluster with the service ip address of the self hosted cluster. The service continues to have no health endpoints because the kubelet can't talk to the apiserver and tell it that the service has healthy endpoints.
So now we have a healthy etcd cluster and no way to update the record in etcd via the apiserver.
The text was updated successfully, but these errors were encountered:
With self hosted etcd we see that significant memory pressure on the masters will cause the cluster to become unstable.
This will mean that the kubelet will eventually mark all the etcd pods unhealthy and thus the kube-proxy will rejecting packets headed for the
kube-system/etcd-service:client
At this point the apiserver is unable to start as it is configured to connect to etcd cluster with the service ip address of the self hosted cluster. The service continues to have no health endpoints because the kubelet can't talk to the apiserver and tell it that the service has healthy endpoints.
So now we have a healthy etcd cluster and no way to update the record in etcd via the apiserver.
The text was updated successfully, but these errors were encountered: