Troubleshooting Issues Cli

Kubectl

API Server Unreachable

Invalid Token in Kubeconfig

Etcdctl

Incorrect Endpoint(s)

Authentication Handshake Failed: EOF

This error may be encountered as a result of an improper or unreachable target within the specified endpoints.

Bash

# ETCDCTL_API=3 etcdctl --cacert /etc/pf9/kube.d/certs/etcdctl/etcd/ca.crt --cert /etc/pf9/kube.d/certs/etcdctl/etcd/request.crt --key /etc/pf9/kube.d/certs/etcdctl/etcd/request.key member list
{"level":"warn","ts":"2021-06-29T17:35:33.700Z","caller":"clientv3/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"endpoint://client-17003473-68d9-4280-9775-c88d055dcab4/127.0.0.1:2379","attempt":0,"error":"rpc error: code = DeadlineExceeded desc = latest balancer error: all SubConns are in TransientFailure, latest connection error: connection error: desc = \"transport: authentication handshake failed: EOF\""}
Error: context deadline exceeded

Specify the --endpoints flag with the local etcd endpoint http://localhost:2379 .

Bash

# ETCDCTL_API=3 etcdctl --cacert /etc/pf9/kube.d/certs/etcdctl/etcd/ca.crt --cert /etc/pf9/kube.d/certs/etcdctl/etcd/request.crt --key /etc/pf9/kube.d/certs/etcdctl/etcd/request.key --endpoints 'http://localhost:2379' member list
bd1ab8ac77aca3e6, started, 9aa28a60-5479-442e-8c06-6ed593be6e8e, https://172.16.0.9:2380, https://172.16.0.9:4001, false
cd520af8c3f07b87, started, 3e687e0c-b974-40e6-9489-ac73087f34ac, https://172.16.0.4:2380, https://172.16.0.4:4001, false
d0ba4097576d2245, started, 20415e06-d528-457b-95da-3b0f2c838624, https://172.16.0.6:2380, https://172.16.0.6:4001, false

Certificates Not Specified

Networking Issues

If your nodes are deployed on an internal network, (e.g. a node deployed on any of the following: AWS or Azure private network, OpenStack tenant network, VMware NSX tenant/private network) you must specify the internal IP of the node as a parameter to the CLI.

If in doubt, run ifconfig on the node, then see what IP address gets reported and specify that IP. Your external IP will not get reported by ifconfig as that is configured external to the node.