Conversation
- old label selectors - etcd doesn't have sh or bash installed, so only direct etcdctl work or the error occurs `error: Internal error occurred: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec "a3897a18d6d4c5464fd16b63355f2e891b74be98d6cea1e26036046f937c94ac": OCI runtime exec failed: exec failed: unable to start container process: exec: "bash": executable file not found in $PATH: unknown`
kubermatic-bot
added
dco-signoff: yes
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/assign @kron4eg |
|
/cc @kron4eg |
|
|
||
| ```bash | ||
| etcdctl member list | ||
| kubectl -n kube-system exec -it etcd-<ALIVE-HOSTNAME> etcdctl --cacert=/etc/kubernetes/pki/etcd/ca.crt --cert=/etc/kubernetes/pki/etcd/healthcheck-client.crt --key=/etc/kubernetes/pki/etcd/healthcheck-client.key member list |
There was a problem hiding this comment.
Hehe, since very recently we've got kubermatic/kubeone#3998 merged, which sets those paths as ENV variables in the etcd pod, which means you don't need to specify any of certificate flags :)
kron4eg
left a comment
kron4eg
left a comment
There was a problem hiding this comment.
Please drop those certs related flags
3 participants
update required due to:
the error occurs
error: Internal error occurred: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec "a3897a18d6d4c5464fd16b63355f2e891b74be98d6cea1e26036046f937c94ac": OCI runtime exec failed: exec failed: unable to start container process: exec: "bash": executable file not found in $PATH: unknown