Execute the command, and then try kubectl get nodes
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $( id -u ) : $( id -g ) $HOME/.kube/config
If not, execute kubectl get nodes –insecure-skip-tls-verify and try
Similar Posts:
- Other Master Nodes Add to the Cluster After Reset Error: CONTEXT DEADLINE EXCEEDED
- [Solved] k8s-nfs pvc load error –nfs-client-provisioner
- K8s version 1.20x nfs dynamic storage error: persistentvolume-controller waiting for a volume to be created, either by external provisioner “qgg-nfs-storage” or manually created by system administrator
- Kubectl’s plug-in management tool Krew
- K8S Error: no metrics known for node [How to Solve]
- [Solved] kubeadm join 192.168.50.66:6443 –token 0109we.c3a3ofn0y0lmp0w9 –discovery-token-ca-cert-hash sha256:262f5eefdbeba51e6875cba5ed6e34061ad679f8a21f6e295d9fbd5ef05757e4
- [Solved] Failed to get node ip address matching nodeport cidr: no addresses found for cidrs [172.16.19.0/24]
- The newly deployed k8s cluster of the virtual machine reports an error when executing kubectl logs and exec
- Raspberry pie: How to Solve Mongodb installation error
- How to Solve nginx Install Error in Mac