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 Mar 28, 2020. It is now read-only.
For this to work we need to ensure that endpoints health would give the same guarantees as a linearizable get, and that it works on an auth enabled cluster.
The text was updated successfully, but these errors were encountered:
Hey @hasbro17 is there any temporary solution to this problem? i.e. what could I do to make the command use endpoints health in the pod configuration? since manually editing it can't work because of permissions (and besides you don't wanna do that).
The current probe used for determining etcd liveliness/health is a linearizable get.
etcd-operator/pkg/util/k8sutil/pod_util.go
Lines 72 to 73 in 3ceb27a
This ensures that the etcd pod is ready to participate in consensus and serve requests.
After auth is enabled on a deployed etcd cluster the etcd-pod's probe will fail since the request is not authenticated.
One solution is to replace the linearizable get with
endpoints health
.https://github.com/coreos/etcd/tree/master/etcdctl#endpoint-health
For this to work we need to ensure that
endpoints health
would give the same guarantees as a linearizable get, and that it works on an auth enabled cluster.The text was updated successfully, but these errors were encountered: