[root@k8s-master ~]# kubectl get po -n kube-system -o wide NAME . . .

Gharbi abdelaziz:
[root@k8s-master ~]# kubectl get po -n kube-system -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
calico-kube-controllers-bcc6f659f-vpt7b 1/1 Running 6 14d 10.244.235.211 k8s-master <none> <none>
calico-node-kqftm 1/1 Running 6 14d 192.168.1.40 k8s-master <none> <none>
calico-node-p7vcc 1/1 Running 6 14d 192.168.1.41 k8s-node <none> <none>
coredns-74ff55c5b-8qk67 1/1 Running 6 14d 10.244.235.212 k8s-master <none> <none>
coredns-74ff55c5b-skrtm 1/1 Running 6 14d 10.244.235.213 k8s-master <none> <none>
etcd-k8s-master 1/1 Running 6 14d 192.168.1.40 k8s-master <none> <none>
kube-apiserver-k8s-master 1/1 Running 9 14d 192.168.1.40 k8s-master <none> <none>
kube-controller-manager-k8s-master 1/1 Running 6 14d 192.168.1.40 k8s-master <none> <none>
kube-proxy-c7ddw 1/1 Running 6 14d 192.168.1.41 k8s-node <none> <none>
kube-proxy-td446 1/1 Running 6 14d 192.168.1.40 k8s-master <none> <none>
kube-scheduler-k8s-master 1/1 Running 6 14d 192.168.1.40 k8s-master <none> <none>

after kubeadm init, export ETCDCTL_API=v3, command ./etcdctl dont work what s go wrong

Ashwin Surendar:
@Gharbi abdelaziz You might need to upgrade your etcdctl version

Ashwin Surendar:
Or prefix it like below

ETCDCTL_API=3 etcdctl get foo

Gharbi abdelaziz:
thank you sir