Kubernetes Node unable to access Docker Private Registry

2/16/2021

I've setup kubernetes cluster which has 3 worker node with docker private registry service. The master node is able to login into Private Registry, but worker nodes can't login due to 503 Service unavailable. There is no error log in the Private Registry pod. How do I debug it?

[root@worker]# docker login -u test -p test123 1.1.1.1:5000
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
Error response from daemon: login attempt to http://1.1.1.1:5000/v2/ failed with status: 503 
Service Unavailable

PS : The Private Registry is insecure so all nodes has insecure-regies: ["1.1.1.1"] configuration. Also I've changed IP addresses. Registry is installed by helm install twuni/docker-registry --generate-name nothing more

-- Naiame Nel'Theri
docker
docker-api
docker-registry
kubernetes

1 Answer

2/18/2021

Solved the issue by setting NO_PROXY environment on all nodes. Apparently the nodes are trying to connect with registry using PROXY even though there was none configured. I found out this by using kubectl describe pod

-- Naiame Nel'Theri
Source: StackOverflow