Kubernetes ingress issue while trying to expose a docker registry pod

Viewed 29

I am trying to configure a private docker registry. The POD is working well, the Service is working well, but the ingress is not.

the pod is using port 5000,

the service yaml is

apiVersion: v1
kind: Service
metadata:
  name: docker-registry
  namespace: docker-registry
  labels:
    k3s-app: docker-registry
spec:
  selector:
    k3s-app: docker-registry
  ports:
    - protocol: TCP
      port: 5555
      targetPort: 5000

when using Cluster IP on port 5555, the pod is logging the connection

the ingress yaml is

kind: Ingress
apiVersion: networking.k8s.io/v1
metadata:
  name: registry-ingress
  namespace: docker-registry
spec:
  rules:
  - host: registry
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: docker-registry
            port:
              number: 5555

host registry is a well defined DNS entry.

from podman I have the following error Error: authenticating creds for "registry": pinging container registry registry: invalid status code from registry 400 (Bad Request)

with the debug logs

DEBU[0002] GET https://registry/v2/                     
DEBU[0002] Ping https://registry/v2/ status 400         
DEBU[0002] GET http://registry/v2/                      
DEBU[0002] Ping http://registry/v2/ status 400          
DEBU[0002] GET https://registry/v1/_ping                
DEBU[0002] Ping https://registry/v1/_ping status 400    
DEBU[0002] GET http://registry/v1/_ping                 
DEBU[0002] Ping http://registry/v1/_ping status 400     
Error: authenticating creds for "registry": pinging container registry registry: invalid status code from registry 400 (Bad Request)

and I have no login attempt on the registry POD.

kubernetes is K3S v1.24.3+k3s1

any help will be appreciated to understand what is going on ..

Thanks

0 Answers
Related