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

This article mainly introduces "how to solve the problem that the domestic K8s ingress-nginx image cannot be pulled properly by pull". In the daily operation, it is believed that many people have doubts about how to solve the problem that the domestic K8s ingress-nginx image cannot be pulled properly by pull. The editor consulted all kinds of materials and sorted out simple and useful operation methods. I hope it will be helpful for you to answer the question "how to solve the problem that the domestic K8s ingress-nginx image cannot be pulled normally by pull"! Next, please follow the editor to study!

I. description of the problem

If we expect to run Ingress, we have to create an Ingress controller for our cluster.

At present, the officially recommended controller are: [currently supports and maintains AWS, GCE and nginx Ingress controllers]

We use nginx controller, and the configuration method given on its official website is as follows:

# instead of using helm, use yamlkubectl apply-f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.1.1/deploy/static/provider/cloud/deploy.yaml

Note that different versions adapt to different K8s versions. See the table for details: (select the supported version according to your K8s version and replace the above v1.1.1, mine is 1.23)

Ingress-NGINX versionk8s supported versionAlpine VersionNginx Versionv1.1.11.23, 1.22,1.21,1.20,1.193.14.21.19.9 "v1.1.01.22,1.21,1.20,1.193.14.21.19.9" v1.0.51.22,1.21,1.20,1.193.14.21.19.9 "v1.0.41.22,1.21,1.20,1.193.14.21.19.9" v1.0.31.22 " 1.21,1.20,1.193.14.21.19.9 "v1.0.21.22,1.21,1.20,1.193.14.21.19.9" v1.0.11.22,1.21,1.20,1.193.14.21.19.9 "v1.0.01.22,1.21,1.20, 1.193.13.51.20.1v0.50.01.21, 1.20 1.193.14.21.19.9 "v0.49.31.21,1.20,1.193.14.21.19.9" v0.49.21.21,1.20,1.193.14.21.19.9 "v0.49.11.21,1.20,1.193.14.21.19.9" v0.49.01.21,1.20, 1.193.13.51.20.1v0.48.11.21, 1.20 1.193.13.51.20.1v0.47.01.21, 1.20, 1.193.13.51.20.1v0.46.01.21, 1.20, 1.193.13.21.19.6

However, the image pulled from the official yaml file is not in docker hub, but in k8s.gcr.io, so we will report an error if we pull it in China: ErrImagePull.

$k describe pod/ingress-nginx-admission-create-8zv9w.Events: Type Reason Age From Message -Normal Scheduled 16m default-scheduler Successfully assigned ingress-nginx/ingress-nginx-admission-create- 8zv9w to node2 Normal SandboxChanged 16m kubelet Pod sandbox changed It will be killed and re-created. Warning Failed 14m (x6 over 16m) kubelet Error: ImagePullBackOff Normal Pulling 14m (x4 over 16m) kubelet Pulling image "k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.1.1@sha256:64d8c73dca984af206adf9d6d7e46aa550362b1d7a01f3a0a91b20cc67868660" Warning Failed 14m (x4 Over 16m) kubelet Failed to pull image "k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.1.1@sha256:64d8c73dca984af206adf9d6d7e46aa550362b1d7a01f3a0a91b20cc67868660": rpc error: code = Unknown desc = Error response from daemon: Get "https://k8s.gcr.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Warning Failed 14m (x4 over 16m) kubelet Error: ErrImagePull Normal BackOff 77s (x58 over 16m) kubelet Back-off pulling image "k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.1.1@sha256:64d8c73dca984af206adf9d6d7e46aa550362b1d7a01f3a0a91b20cc67868660"

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.