Shulou(Shulou.com)05/31 Report--

This article mainly shows you "what are the common problems in kubernetes", which is easy to understand and well organized. I hope it can help you solve your doubts. Let the editor lead you to study and learn the article "what are the common problems in kubernetes".

Why does it take more than 5 minutes to reschedule Pod in the event of a node failure?

This is due to a combination of the following default Kubernetes settings:

Kubelet

Node-status-update-frequency: specifies how often kubelet publishes node status to master (default is 10 seconds)

Kube-controller-manager

Node-monitor-period: the time period for synchronizing NodeStatus in NodeController (default is 5 seconds)

Node-monitor-grace-period: the time it takes to allow the running node to become unresponsive before marking it as unhealthy (default is 40 seconds)

Pod-eviction-timeout: Grace period for deleting Pod on failed nodes (default is 5m0)

For more information about these settings, visit the documentation: quickly migrate Pods when nodes are unavailable

Network: stat / var/lib/calico/nodename: no such file or directory

When the calico service starts, the nodename file is generated in the / var/lib/calico/ directory, which also corresponds to this path on the host. There are multiple containers in calico pod, and there are containers responsible for generating the nodename file. If this problem occurs, it is possible that the container is not working properly. You can delete the Pod and let it run again, or initialize the node according to the following document and then add it to the cluster again: https://www.xtplayer.cn/rancher/node-init/

[controlPlane] Failed to bring up Control Plane:Failed to verify healthcheck

This is a common error, which is usually caused by the failure of the kube-apiserver or kube-controller-manager service to pass the rke health check.

In rke1, kube-apiserver or kube-controller-manager is run as a docker run container. You can view the container log through docker logs kube-apiserver-- tail 100-f or docker logs kube-controller-manager-- tail 100-f to further determine the cause of the problem.

Failed to bring up worker plane

This is a common error, which is usually caused by the failure of the kubelet service to pass the rke health check.

In rke1, kubelet runs as a docker run container, and you can view the container log through docker logs kubelet-- tail 100-f to further determine the cause of the problem.

Runtime network not ready: NetworkReady=falseRuntime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized

The rancher kubernetes network driver runs as a container. If the deployment environment is slow, it will take a long time to download the image, thus affecting the driver deployment. The above error message is prompted because the system timed out. Usually wait 5 to 10 minutes to automatically return to normal.

If you wait a long time and fail to return to normal, then this should be caused by the abnormal operation of the driver. You can delete the network driver Pod to recreate it with the following command:

Kubectl-n kube-system get pod | awk'{print $1}'| grep-E 'canal | calico | flannel' | xargs kubectl-n kube-system delete pod

The above is all the content of the article "what are the kubernetes FAQs?" Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

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.