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

This article mainly explains "common problems and solutions in Kubernetes cluster environment". The content of the explanation is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "common problems and solutions in Kubernetes cluster environment".

1. Each node image cannot be pulled automatically in Kubernetes cluster environment.

In general, in this case, the stupid way is to log in to each node through human flesh and get the image in the form of docker login docker pull. Imagine if there are hundreds of nodes.

Generally, such problems are solved in private warehouses and cloud vendors as follows.

Clusters with proprietary images, such as private warehouses built by some individuals or companies, here are the steps to solve this problem

Docker login [server] runs for each set of credentials to be used. This will update $HOME/.docker/config.json

$HOME/.docker/config.json is viewed in the editor to make sure it contains only the credentials you want to use

Copy the current node .docker / config.json to another node with the following command

For n in $nodes; do scp ~ / .docker/config.json root@$n:/var/lib/kubelet/config.json; done

4. Create a pod test pull image

Kubectl apply-f-

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.