You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use the combination "k8s" + "spegel" + "nexus" -> as pull-through-cache. Nexus is secured with basic-auth and the authentication has been added through k8s "imagePullSecrets".
Within the k8s Secret we defined the authentication for the registry name "nexus.ourdomain".
The problem is that the authentication is not getting used due to different container registry names.
For example: if pulling an image with name "kubectl" credentials are being search for "docker.io/kubectl" and not "nexus.ourdomain/kubectl" but the additional registry mirror(nexus.ourdomain) is being used which then gets rejected.
Proposed solution to the problem
The only workaround I found was to add the nexus auth data to the domain "docker.io", which in itself is definitely no solution.
Any help is appreciated.
The text was updated successfully, but these errors were encountered:
Describe the problem to be solved
We use the combination "k8s" + "spegel" + "nexus" -> as pull-through-cache. Nexus is secured with basic-auth and the authentication has been added through k8s "imagePullSecrets".
Within the k8s Secret we defined the authentication for the registry name "nexus.ourdomain".
The problem is that the authentication is not getting used due to different container registry names.
For example: if pulling an image with name "kubectl" credentials are being search for "docker.io/kubectl" and not "nexus.ourdomain/kubectl" but the additional registry mirror(nexus.ourdomain) is being used which then gets rejected.
Proposed solution to the problem
The only workaround I found was to add the nexus auth data to the domain "docker.io", which in itself is definitely no solution.
Any help is appreciated.
The text was updated successfully, but these errors were encountered: