I’m trying to configure registry in my fresh rancher 2.0 installation.
I created a cluster and in Default >> Resources >> Registries, I added my private registry with scope “Available to all namespaces in this project”.
The registry is a Nexus where I created the kubernetes user. When I try to deploy a pod using this registry, I got :
3s 18s 2 spring-cloud-config-c9dddbd6c-4dsnv.15313e7861d9f8a5 Pod spec.containers{spring-cloud-config} Warning Failed kubelet, cebesvc-ba5tit8 Failed to pull image “myregistry.com:5000/spring-cloud-config:0.1”: rpc error: code = Unknown desc = Error: image spring-cloud-config:0.1 not found
I have the impression that the configuration I did in the UI is not really good configured at the cluster level.
Note : I logged in ssh on one of my node, I did a docker login myregistry.com:5000 with the same user than which used in the rancher registries config and I pulled my image successfully.
Note 2 : I still have a rancher 1.6 cluster and it’s working there.
Did I missed something in my configuration in rancher 2.0 ?
Not sure how you created a registry with a name like myregistry.com - for me it refused the . - so my registry is just called myregistry.
The solution of imagePullSecrets solved it for me, as last for now. I would think it’s not necessary to put this in, but at the same time, it’s not illogical because you could have different teams I guess with different access.
The issue is currently assigned to the September milestone. Hopefully, it will get fixed then. Only workaround so far is to manually add “imagePullSecrets:…” to each workload YAML definition.