CODEWITHSUNDEEP
kubernetescluster-computingdocker-registry
Seb tummi tetred13
Seb tummi tetred13

Reputation: 11

K8S PODS from workers can not access to private repository deployed on Master

I have created a K8S Cluster with 3 nodes ( 1 Master + 2 Workers / CNI flannel).

I have deployed a private repository localhost:31320 on Master using docker registry ( secret has been correctly defined in deployment registry file).

My issue is that I can not pull image from private registry ( it works correctly on Master) I get error:

"Warning Failed 4m15s (x6 over 22m) kubelet Failed to pull image "localhost:31320/automation-platform/base:11.0.15.1.centos.7.9.2009.2": rpc error: code = Unknown desc = Error while pulling image: Get http://localhost:31320/v1/repositories/automation-platform/base/images: dial tcp [::1]:31320: connect: connection refused "

I do not know how to investigate it and why my workers does not acces to private repo ( connection refused ?) I don't see any error under kubelet logs of worker node.

Note that my deployment files have been already used on a previous network and all worked correctly. The difference I saw is that I used K8S 1.20. Now, I use K8S 1.23

Does someone could tell how I can investigate to see the reason of my problem ?

Regards,

Upvotes: 1

Views: 447

Answers (1)

Amirhossein eidy
Amirhossein eidy

Reputation: 19

try to edit /etc/containerd/config.toml and add your registry ip:port like this { "insecure-registries": ["172.16.4.93:5000"] }

Upvotes: 0

Related Questions