Shulou(Shulou.com)06/02 Report--

1. Sep 15 18:22:07 k8s-node1 kubelet: E0915 18 virtual 22 summary.go:102 07.628384 12912 summary.go:102] Failed to get system container stats for "/ system.slice/kubelet.service": failed to get cgroup stats for "/ system.slice/kubelet.service": failed to get container info for "/ system.slice/kubelet.service": unknown container "/ system.slice/kubelet.service

Docker needs to restart

2 、

[discovery] Failed to request cluster info, will try again: [Get https://192.168.1.112:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: x509: certificate has expired or is not yet valid

It is incorrect for a single node to join the time zone. The time ntpdate 182.92.12.11 under ntpupdate is required.

3 、

If the kubectl get nodes has a node whose state is not ready, restart the docker of that node

The prompt to execute kubectl get nodes is as follows:

Unable to connect to the server: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "kubernetes")

For the solution, remember that the kubeadm reset will be deleted:

4 、

Error: open / var/lib/kubelet/config.yaml: no such file or directory

The key files are missing, most of which occur when systemctl start kubelet is run without kubeadm init.

5 、

Kubeadm init-apiserver-advertise-address=192.168.11.12-image-repository registry.aliyuncs.com/google_containers-kubernetes-version v1.13.4-pod-network-cidr=10.244.0.0/16

Kubernete v1.13.4 can specify a source for installation

6 、

Kubernete v1.13.4 supports docker-ce-18.06.3.ce-3.el7.x86_64

7 、

Kubectl get pod-- all-namespaces-o wide

Make sure that the cluster enters the running state and then check the cluster status, otherwise it may not be normal. This will take a few minutes.

8 、

Swapoff | # / dev/mapper/centos-swap swap swap defaults 0 0

Turn off the swap swap partition, and the swap partition technology is now basically unused.

9. The kubeadm reset command, kubeadm reset, will be used repeatedly

10 、

Kubectl drain node2-delete-local-data-force-ignore-daemonsets

Kubectl delete node node2

Kubeadm join 192.168.11.12 6443-token vabefc.eilf71g7y96twbyz-discovery-token-ca-cert-hash sha256:4e6f2149e6488be130611ccc92137cdaf7a3c64a919c4454604f9857d51453a7

Cluster joins nodes and deletes nodes

# k8s question summary

Https://blog.csdn.net/qq_34857250/article/details/82562514

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.