相關查詢命令
查詢docker版本
[root@node1 /root]# docker version
Client:
Version: 17.03.2-ce
API version: 1.27
Go version: go1.7.5
Git commit: f5ec1e2
Built: Tue Jun 27 02:21:36 2017
OS/Arch: linux/amd64
Server:
Version: 17.03.2-ce
API version: 1.27 (minimum version 1.12)
Go version: go1.7.5
Git commit: f5ec1e2
Built: Tue Jun 27 02:21:36 2017
OS/Arch: linux/amd64
Experimental: false
查詢kubeadm版本
[root@node1 /root]# kubeadm version
kubeadm version: &version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.0", GitCommit:"925c127ec6b946659ad0fd596fa959be43f0cc05", GitTreeState:"clean", BuildDate:"2017-12-15T20:55:30Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}
查詢kubelet版本
[root@node1 /root]# kubelet –version
Kubernetes v1.9.0
查詢k8s集群節點狀態
[root@node1 /root]# kubectl get nodes -o wide
NAME STATUS ROLES AGE VERSION EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
node1 Ready master 17h v1.9.0 <none> CentOS Linux 7 (Core) 3.10.0-514.el7.x86_64 docker://17.3.2
node2 Ready <none> 16h v1.9.0 <none> CentOS Linux 7 (Core) 3.10.0-514.el7.x86_64 docker://17.3.2
node3 Ready <none> 16h v1.9.0 <none> CentOS Linux 7 (Core) 3.10.0-514.el7.x86_64 docker://17.3.2
node4 Ready <none> 16h v1.9.0 <none> CentOS Linux 7 (Core) 3.10.0-514.el7.x86_64 docker://17.3.2
node5 Ready <none> 16h v1.9.0 <none> CentOS Linux 7 (Core) 3.10.0-514.el7.x86_64 docker://17.3.2
查詢節點詳細訊息
[root@node1 /root]# kubectl describe nodes
Name: node1
Roles: master
Labels: beta.kubernetes.io/arch=amd64
beta.kubernetes.io/os=linux
kubernetes.io/hostname=node1
node-role.kubernetes.io/master=
Annotations: flannel.alpha.coreos.com/backend-data={"VtepMAC":"2e:58:7c:f8:47:a2"}
flannel.alpha.coreos.com/backend-type=vxlan
flannel.alpha.coreos.com/kube-subnet-manager=true
flannel.alpha.coreos.com/public-ip=172.172.20.33
node.alpha.kubernetes.io/ttl=0
volumes.kubernetes.io/controller-managed-attach-detach=true
Taints: node-role.kubernetes.io/master:NoSchedule
CreationTimestamp: Wed, 27 Dec 2017 16:01:23 +0800
Conditions:
Type Status LastHeartbeatTime LastTransitionTime Reason Message
—- —— —————– —————— —— ——-
OutOfDisk False Thu, 28 Dec 2017 09:16:23 +0800 Wed, 27 Dec 2017 16:01:13 +0800 KubeletHasSufficientDisk kubelet has sufficient disk space available
MemoryPressure False Thu, 28 Dec 2017 09:16:23 +0800 Wed, 27 Dec 2017 16:01:13 +0800 KubeletHasSufficientMemory kubelet has sufficient memory available
DiskPressure False Thu, 28 Dec 2017 09:16:23 +0800 Wed, 27 Dec 2017 16:01:13 +0800 KubeletHasNoDiskPressure kubelet has no disk pressure
Ready True Thu, 28 Dec 2017 09:16:23 +0800 Wed, 27 Dec 2017 16:14:43 +0800 KubeletReady kubelet is posting ready status
Addresses:
InternalIP: 172.172.20.33
Hostname: node1
Capacity:
cpu: 4
memory: 7994312Ki
pods: 110
Allocatable:
cpu: 4
memory: 7891912Ki
pods: 110
System Info:
Machine ID: 1f5195b3a4a642dd8a91265a6b6ea308
System UUID: 4217AC16-AF08-6B2F-D705-12754A6D1E9C
Boot ID: c5c071ef-e255-4f41-81a0-abea5e31ad65
Kernel Version: 3.10.0-514.el7.x86_64
OS Image: CentOS Linux 7 (Core)
Operating System: linux
Architecture: amd64
Container Runtime Version: docker://17.3.2
Kubelet Version: v1.9.0
Kube-Proxy Version: v1.9.0
PodCIDR: 10.244.0.0/24
ExternalID: node1
Non-terminated Pods: (7 in total)
Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits
——— —- ———— ———- ————— ————-
kube-system etcd-node1 0 (0%) 0 (0%) 0 (0%) 0 (0%)
kube-system kube-apiserver-node1 250m (6%) 0 (0%) 0 (0%) 0 (0%)
kube-system kube-controller-manager-node1 200m (5%) 0 (0%) 0 (0%) 0 (0%)
kube-system kube-dns-6f4fd4bdf-jzgsd 260m (6%) 0 (0%) 110Mi (1%) 170Mi (2%)
kube-system kube-flannel-ds-jbxs6 100m (2%) 100m (2%) 50Mi (0%) 50Mi (0%)
kube-system kube-proxy-zfwk8 0 (0%) 0 (0%) 0 (0%) 0 (0%)
kube-system kube-scheduler-node1 100m (2%) 0 (0%) 0 (0%) 0 (0%)
Allocated resources:
(Total limits may be over 100 percent, i.e., overcommitted.)
CPU Requests CPU Limits Memory Requests Memory Limits
———— ———- ————— ————-
910m (22%) 100m (2%) 160Mi (2%) 220Mi (2%)
Events: <none>
Name: node2
Roles: <none>
Labels: beta.kubernetes.io/arch=amd64
beta.kubernetes.io/os=linux
kubernetes.io/hostname=node2
Annotations: flannel.alpha.coreos.com/backend-data={"VtepMAC":"8a:1b:4b:fe:ea:18"}
flannel.alpha.coreos.com/backend-type=vxlan
flannel.alpha.coreos.com/kube-subnet-manager=true
flannel.alpha.coreos.com/public-ip=172.172.20.34
node.alpha.kubernetes.io/ttl=0
volumes.kubernetes.io/controller-managed-attach-detach=true
Taints: <none>
CreationTimestamp: Wed, 27 Dec 2017 16:33:48 +0800
Conditions:
Type Status LastHeartbeatTime LastTransitionTime Reason Message
—- —— —————– —————— —— ——-
OutOfDisk False Thu, 28 Dec 2017 09:16:29 +0800 Wed, 27 Dec 2017 16:33:48 +0800 KubeletHasSufficientDisk kubelet has sufficient disk space available
MemoryPressure False Thu, 28 Dec 2017 09:16:29 +0800 Wed, 27 Dec 2017 16:33:48 +0800 KubeletHasSufficientMemory kubelet has sufficient memory available
DiskPressure False Thu, 28 Dec 2017 09:16:29 +0800 Wed, 27 Dec 2017 16:33:48 +0800 KubeletHasNoDiskPressure kubelet has no disk pressure
Ready True Thu, 28 Dec 2017 09:16:29 +0800 Wed, 27 Dec 2017 16:33:58 +0800 KubeletReady kubelet is posting ready status
Addresses:
InternalIP: 172.172.20.34
Hostname: node2
Capacity:
cpu: 4
memory: 7994312Ki
pods: 110
Allocatable:
cpu: 4
memory: 7891912Ki
pods: 110
System Info:
Machine ID: 1f5195b3a4a642dd8a91265a6b6ea308
System UUID: 42170119-412E-9861-5B92-FB2DC46155CA
Boot ID: 2ad6ea69-e6a4-499b-9fb2-9c75ceed5732
Kernel Version: 3.10.0-514.el7.x86_64
OS Image: CentOS Linux 7 (Core)
Operating System: linux
Architecture: amd64
Container Runtime Version: docker://17.3.2
Kubelet Version: v1.9.0
Kube-Proxy Version: v1.9.0
PodCIDR: 10.244.1.0/24
ExternalID: node2
Non-terminated Pods: (3 in total)
Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits
——— —- ———— ———- ————— ————-
kube-system kube-flannel-ds-wrtp7 100m (2%) 100m (2%) 50Mi (0%) 50Mi (0%)
kube-system kube-proxy-px8g8 0 (0%) 0 (0%) 0 (0%) 0 (0%)
kube-system monitoring-influxdb-6c4b84d695-cnfc9 0 (0%) 0 (0%) 0 (0%) 0 (0%)
Allocated resources:
(Total limits may be over 100 percent, i.e., overcommitted.)
CPU Requests CPU Limits Memory Requests Memory Limits
———— ———- ————— ————-
100m (2%) 100m (2%) 50Mi (0%) 50Mi (0%)
Events: <none>
Name: node3
Roles: <none>
Labels: beta.kubernetes.io/arch=amd64
beta.kubernetes.io/os=linux
kubernetes.io/hostname=node3
Annotations: flannel.alpha.coreos.com/backend-data={"VtepMAC":"5e:62:6a:95:9e:fd"}
flannel.alpha.coreos.com/backend-type=vxlan
flannel.alpha.coreos.com/kube-subnet-manager=true
flannel.alpha.coreos.com/public-ip=172.172.20.35
node.alpha.kubernetes.io/ttl=0
volumes.kubernetes.io/controller-managed-attach-detach=true
Taints: <none>
CreationTimestamp: Wed, 27 Dec 2017 16:34:59 +0800
Conditions:
Type Status LastHeartbeatTime LastTransitionTime Reason Message
—- —— —————– —————— —— ——-
OutOfDisk False Thu, 28 Dec 2017 09:16:30 +0800 Wed, 27 Dec 2017 16:34:59 +0800 KubeletHasSufficientDisk kubelet has sufficient disk space available
MemoryPressure False Thu, 28 Dec 2017 09:16:30 +0800 Wed, 27 Dec 2017 16:34:59 +0800 KubeletHasSufficientMemory kubelet has sufficient memory available
DiskPressure False Thu, 28 Dec 2017 09:16:30 +0800 Wed, 27 Dec 2017 16:34:59 +0800 KubeletHasNoDiskPressure kubelet has no disk pressure
Ready True Thu, 28 Dec 2017 09:16:30 +0800 Wed, 27 Dec 2017 16:35:09 +0800 KubeletReady kubelet is posting ready status
Addresses:
InternalIP: 172.172.20.35
Hostname: node3
Capacity:
cpu: 4
memory: 7994312Ki
pods: 110
Allocatable:
cpu: 4
memory: 7891912Ki
pods: 110
System Info:
Machine ID: 1f5195b3a4a642dd8a91265a6b6ea308
System UUID: 4217F8F2-CF33-91DD-1A3B-EB34BCC6BFCE
Boot ID: 32753ab6-854a-4d90-8df7-dffea4421749
Kernel Version: 3.10.0-514.el7.x86_64
OS Image: CentOS Linux 7 (Core)
Operating System: linux
Architecture: amd64
Container Runtime Version: docker://17.3.2
Kubelet Version: v1.9.0
Kube-Proxy Version: v1.9.0
PodCIDR: 10.244.2.0/24
ExternalID: node3
Non-terminated Pods: (3 in total)
Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits
——— —- ———— ———- ————— ————-
kube-system kube-flannel-ds-lk2hm 100m (2%) 100m (2%) 50Mi (0%) 50Mi (0%)
kube-system kube-proxy-gbcxp 0 (0%) 0 (0%) 0 (0%) 0 (0%)
kube-system monitoring-grafana-76848b566c-vh2qb 0 (0%) 0 (0%) 0 (0%) 0 (0%)
Allocated resources:
(Total limits may be over 100 percent, i.e., overcommitted.)
CPU Requests CPU Limits Memory Requests Memory Limits
———— ———- ————— ————-
100m (2%) 100m (2%) 50Mi (0%) 50Mi (0%)
Events: <none>
Name: node4
Roles: <none>
Labels: beta.kubernetes.io/arch=amd64
beta.kubernetes.io/os=linux
kubernetes.io/hostname=node4
Annotations: flannel.alpha.coreos.com/backend-data={"VtepMAC":"26:cd:79:7b:0d:33"}
flannel.alpha.coreos.com/backend-type=vxlan
flannel.alpha.coreos.com/kube-subnet-manager=true
flannel.alpha.coreos.com/public-ip=172.172.20.36
node.alpha.kubernetes.io/ttl=0
volumes.kubernetes.io/controller-managed-attach-detach=true
Taints: <none>
CreationTimestamp: Wed, 27 Dec 2017 16:35:04 +0800
Conditions:
Type Status LastHeartbeatTime LastTransitionTime Reason Message
—- —— —————– —————— —— ——-
OutOfDisk False Thu, 28 Dec 2017 09:16:22 +0800 Wed, 27 Dec 2017 16:35:04 +0800 KubeletHasSufficientDisk kubelet has sufficient disk space available
MemoryPressure False Thu, 28 Dec 2017 09:16:22 +0800 Wed, 27 Dec 2017 16:35:04 +0800 KubeletHasSufficientMemory kubelet has sufficient memory available
DiskPressure False Thu, 28 Dec 2017 09:16:22 +0800 Wed, 27 Dec 2017 16:35:04 +0800 KubeletHasNoDiskPressure kubelet has no disk pressure
Ready True Thu, 28 Dec 2017 09:16:22 +0800 Wed, 27 Dec 2017 16:35:14 +0800 KubeletReady kubelet is posting ready status
Addresses:
InternalIP: 172.172.20.36
Hostname: node4
Capacity:
cpu: 4
memory: 7994312Ki
pods: 110
Allocatable:
cpu: 4
memory: 7891912Ki
pods: 110
System Info:
Machine ID: 1f5195b3a4a642dd8a91265a6b6ea308
System UUID: 421770E6-E33A-B8C2-9CE2-916B687B7F17
Boot ID: 98230be6-49f3-4044-9729-fa989666dd05
Kernel Version: 3.10.0-514.el7.x86_64
OS Image: CentOS Linux 7 (Core)
Operating System: linux
Architecture: amd64
Container Runtime Version: docker://17.3.2
Kubelet Version: v1.9.0
Kube-Proxy Version: v1.9.0
PodCIDR: 10.244.3.0/24
ExternalID: node4
Non-terminated Pods: (3 in total)
Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits
——— —- ———— ———- ————— ————-
kube-system kube-flannel-ds-jrdqp 100m (2%) 100m (2%) 50Mi (0%) 50Mi (0%)
kube-system kube-proxy-hdx5m 0 (0%) 0 (0%) 0 (0%) 0 (0%)
kube-system kubernetes-dashboard-7b7b5cd79b-mnwn2 0 (0%) 0 (0%) 0 (0%) 0 (0%)
Allocated resources:
(Total limits may be over 100 percent, i.e., overcommitted.)
CPU Requests CPU Limits Memory Requests Memory Limits
———— ———- ————— ————-
100m (2%) 100m (2%) 50Mi (0%) 50Mi (0%)
Events: <none>
Name: node5
Roles: <none>
Labels: beta.kubernetes.io/arch=amd64
beta.kubernetes.io/os=linux
kubernetes.io/hostname=node5
Annotations: flannel.alpha.coreos.com/backend-data={"VtepMAC":"6e:c6:96:c9:00:6e"}
flannel.alpha.coreos.com/backend-type=vxlan
flannel.alpha.coreos.com/kube-subnet-manager=true
flannel.alpha.coreos.com/public-ip=172.172.20.37
node.alpha.kubernetes.io/ttl=0
volumes.kubernetes.io/controller-managed-attach-detach=true
Taints: <none>
CreationTimestamp: Wed, 27 Dec 2017 16:35:07 +0800
Conditions:
Type Status LastHeartbeatTime LastTransitionTime Reason Message
—- —— —————– —————— —— ——-
OutOfDisk False Thu, 28 Dec 2017 09:16:26 +0800 Wed, 27 Dec 2017 16:35:07 +0800 KubeletHasSufficientDisk kubelet has sufficient disk space available
MemoryPressure False Thu, 28 Dec 2017 09:16:26 +0800 Wed, 27 Dec 2017 16:35:07 +0800 KubeletHasSufficientMemory kubelet has sufficient memory available
DiskPressure False Thu, 28 Dec 2017 09:16:26 +0800 Wed, 27 Dec 2017 16:35:07 +0800 KubeletHasNoDiskPressure kubelet has no disk pressure
Ready True Thu, 28 Dec 2017 09:16:26 +0800 Wed, 27 Dec 2017 16:35:17 +0800 KubeletReady kubelet is posting ready status
Addresses:
InternalIP: 172.172.20.37
Hostname: node5
Capacity:
cpu: 4
memory: 7994312Ki
pods: 110
Allocatable:
cpu: 4
memory: 7891912Ki
pods: 110
System Info:
Machine ID: 1f5195b3a4a642dd8a91265a6b6ea308
System UUID: 4217822B-3785-632F-A650-49C9E54B430C
Boot ID: 0b05b550-d61a-46f5-b9c4-75868725fe1a
Kernel Version: 3.10.0-514.el7.x86_64
OS Image: CentOS Linux 7 (Core)
Operating System: linux
Architecture: amd64
Container Runtime Version: docker://17.3.2
Kubelet Version: v1.9.0
Kube-Proxy Version: v1.9.0
PodCIDR: 10.244.4.0/24
ExternalID: node5
Non-terminated Pods: (4 in total)
Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits
——— —- ———— ———- ————— ————-
default curl-545bbf5f9c-7l6bv 0 (0%) 0 (0%) 0 (0%) 0 (0%)
kube-system heapster-dfd674df9-mgvf4 0 (0%) 0 (0%) 0 (0%) 0 (0%)
kube-system kube-flannel-ds-mnfrs 100m (2%) 100m (2%) 50Mi (0%) 50Mi (0%)
kube-system kube-proxy-kmngl 0 (0%) 0 (0%) 0 (0%) 0 (0%)
Allocated resources:
(Total limits may be over 100 percent, i.e., overcommitted.)
CPU Requests CPU Limits Memory Requests Memory Limits
———— ———- ————— ————-
100m (2%) 100m (2%) 50Mi (0%) 50Mi (0%)
Events: <none>
查詢pod服務狀態
[root@node1 /root]# kubectl get pods --all-namespaces -o wide
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE
default curl-545bbf5f9c-7l6bv 1/1 Running 1 16h 10.244.4.2 node5
kube-system etcd-node1 1/1 Running 0 17h 172.172.20.33 node1
kube-system heapster-dfd674df9-mgvf4 1/1 Running 0 15h 10.244.4.3 node5
kube-system kube-apiserver-node1 1/1 Running 0 17h 172.172.20.33 node1
kube-system kube-controller-manager-node1 1/1 Running 0 17h 172.172.20.33 node1
kube-system kube-dns-6f4fd4bdf-jzgsd 3/3 Running 0 17h 10.244.0.2 node1
kube-system kube-flannel-ds-jbxs6 1/1 Running 0 17h 172.172.20.33 node1
kube-system kube-flannel-ds-jrdqp 1/1 Running 0 16h 172.172.20.36 node4
kube-system kube-flannel-ds-lk2hm 1/1 Running 0 16h 172.172.20.35 node3
kube-system kube-flannel-ds-mnfrs 1/1 Running 0 16h 172.172.20.37 node5
kube-system kube-flannel-ds-wrtp7 1/1 Running 0 16h 172.172.20.34 node2
kube-system kube-proxy-gbcxp 1/1 Running 0 16h 172.172.20.35 node3
kube-system kube-proxy-hdx5m 1/1 Running 0 16h 172.172.20.36 node4
kube-system kube-proxy-kmngl 1/1 Running 0 16h 172.172.20.37 node5
kube-system kube-proxy-px8g8 1/1 Running 0 16h 172.172.20.34 node2
kube-system kube-proxy-zfwk8 1/1 Running 0 17h 172.172.20.33 node1
kube-system kube-scheduler-node1 1/1 Running 0 17h 172.172.20.33 node1
kube-system kubernetes-dashboard-7b7b5cd79b-mnwn2 1/1 Running 0 16h 10.244.3.2 node4
kube-system monitoring-grafana-76848b566c-vh2qb 1/1 Running 0 15h 10.244.2.2 node3
kube-system monitoring-influxdb-6c4b84d695-cnfc9 1/1 Running 0 15h 10.244.1.2 node2
[root@node1 /root]# kubectl cluster-info
Kubernetes master is running at https://172.172.20.33:6443
Heapster is running at https://172.172.20.33:6443/api/v1/namespaces/kube-system/services/heapster/proxy
KubeDNS is running at https://172.172.20.33:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
monitoring-grafana is running at https://172.172.20.33:6443/api/v1/namespaces/kube-system/services/monitoring-grafana/proxy
monitoring-influxdb is running at https://172.172.20.33:6443/api/v1/namespaces/kube-system/services/monitoring-influxdb/proxy
查看master所有token
[root@node1 /root]# kubectl get secret -n kube-system
NAME TYPE DATA AGE
attachdetach-controller-token-w4vxr kubernetes.io/service-account-token 3 17h
bootstrap-signer-token-z2fqz kubernetes.io/service-account-token 3 17h
bootstrap-token-8c4e6c bootstrap.kubernetes.io/token 7 17h
certificate-controller-token-4hp62 kubernetes.io/service-account-token 3 17h
clusterrole-aggregation-controller-token-fscmr kubernetes.io/service-account-token 3 17h
cronjob-controller-token-v9rxh kubernetes.io/service-account-token 3 17h
daemon-set-controller-token-9f5mq kubernetes.io/service-account-token 3 17h
default-token-6mslb kubernetes.io/service-account-token 3 17h
deployment-controller-token-hz4zh kubernetes.io/service-account-token 3 17h
disruption-controller-token-g9dlg kubernetes.io/service-account-token 3 17h
endpoint-controller-token-xn4pv kubernetes.io/service-account-token 3 17h
flannel-token-x7nm2 kubernetes.io/service-account-token 3 17h
generic-garbage-collector-token-46prh kubernetes.io/service-account-token 3 17h
heapster-token-p9tp6 kubernetes.io/service-account-token 3 16h
horizontal-pod-autoscaler-token-w7tj8 kubernetes.io/service-account-token 3 17h
job-controller-token-r7nrq kubernetes.io/service-account-token 3 17h
kube-dns-token-l7dd4 kubernetes.io/service-account-token 3 17h
kube-proxy-token-92vws kubernetes.io/service-account-token 3 17h
kubernetes-dashboard-admin-token-c2ftm kubernetes.io/service-account-token 3 16h
kubernetes-dashboard-certs Opaque 0 16h
kubernetes-dashboard-key-holder Opaque 2 16h
kubernetes-dashboard-token-442dj kubernetes.io/service-account-token 3 16h
namespace-controller-token-gh6hs kubernetes.io/service-account-token 3 17h
node-controller-token-wlckn kubernetes.io/service-account-token 3 17h
persistent-volume-binder-token-j2thl kubernetes.io/service-account-token 3 17h
pod-garbage-collector-token-sfspr kubernetes.io/service-account-token 3 17h
replicaset-controller-token-kgdbq kubernetes.io/service-account-token 3 17h
replication-controller-token-55t6p kubernetes.io/service-account-token 3 17h
resourcequota-controller-token-whsgm kubernetes.io/service-account-token 3 17h
service-account-controller-token-gqkwh kubernetes.io/service-account-token 3 17h
service-controller-token-fnj65 kubernetes.io/service-account-token 3 17h
statefulset-controller-token-28bst kubernetes.io/service-account-token 3 17h
token-cleaner-token-cftj9 kubernetes.io/service-account-token 3 17h
ttl-controller-token-w6mm7 kubernetes.io/service-account-token 3 17h
查看具體token訊息
[root@node1 /root]# kubectl describe secret/flannel-token-x7nm2 -n kube-system
Name: flannel-token-x7nm2
Namespace: kube-system
Labels: <none>
Annotations: kubernetes.io/service-account.name=flannel
kubernetes.io/service-account.uid=f869fba9-eadd-11e7-8c16-005056975b01
Type: kubernetes.io/service-account-token
Data
====
ca.crt: 1025 bytes
namespace: 11 bytes
token: eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9uYW1lc3BhY2UiOiJrdWJlLXN5c3RlbSIsImt1YmVybmV0ZXMuaW8vc2VydmljZWFjY291bnQvc2VjcmV0Lm5hbWUiOiJmbGFubmVsLXRva2VuLXg3bm0yIiwia3ViZXJuZXRlcy5pby9zZXJ2aWNlYWNjb3VudC9zZXJ2aWNlLWFjY291bnQubmFtZSI6ImZsYW5uZWwiLCJrdWJlcm5ldGVzLmlvL3NlcnZpY2VhY2NvdW50L3NlcnZpY2UtYWNjb3VudC51aWQiOiJmODY5ZmJhOS1lYWRkLTExZTctOGMxNi0wMDUwNTY5NzViMDEiLCJzdWIiOiJzeXN0ZW06c2VydmljZWFjY291bnQ6a3ViZS1zeXN0ZW06Zmxhbm5lbCJ9.cMeU2LQSU7DXGFaery3i_tQft_Hk-lOQqg3ixlVcpDjwo-CCOSgrlll2Q0Et-dLKJT9mhiTOPjkqzcIIwtB10Xg3umdQGExqWdlQCOGbk2tvqOMMp44B2O0spsu41Pxi-F5euGQA_88wIl26Egw28knXJEyb-SphSspM01kxLdGExG1GTXYhHeBi8RGPxEIMKCQ9_cfd5WNyjthdnY4wUErGYxv9x-dgiOufc6syfImKj27bFEGrQSQMOyni17B20xJMuiLktuZmydm1vIglBIKlbaeaLEKK2GZmsl-LefdG4fMA-pZZfgZspNeg-Nft1weaozRpIjsmVZlFq11mMw
Cleanup and reinitialize cluster
kubeadm reset
ifconfig cni0 down
ip link delete cni0
ifconfig flannel.1 down
ip link delete flannel.1
rm -rf /var/lib/cni/