This message was deleted.
# rke2a
adamant-kite-43734
03/26/2023, 9:20 PMThis message was deleted.
c
creamy-pencil-82913
03/27/2023, 2:39 AMIf they are both mirroring docker hub, just list them both in the endpoint list
h
hallowed-breakfast-56871
03/27/2023, 2:41 AMHmm, I did try this. but it failed. I'd need to check the log.
Is this the right format?
Copy code
configs:
<http://registry-1.docker.io|registry-1.docker.io>:
auth:
username: 1
password: pass
<http://registry-1.docker.io|registry-1.docker.io>:
auth:
username: 2
password: wordcreamy-pencil-82913
03/27/2023, 6:16 AMCan you confirm exactly what you're trying to accomplish?
h
hallowed-breakfast-56871
03/27/2023, 6:20 AMWe have 2 docker hub orgs. One for each platform we host.
Our clusters, need to be able to pull private images from both these private docker hub repositories.
This is a temporary situation, as we have just acquired one of these platforms from a acquisition. I have plans in place to merge the CI/CD for the two platforms.... but that's going to be 6-8 months away.
c
creamy-pencil-82913
03/27/2023, 6:24 AMAh. That is not what mirrors are for then.
creamy-pencil-82913
03/27/2023, 6:25 AMAnd you cannot use registries.yaml to configure multiple credentials. If you're going to put your creds in registries.yaml those creds need to be able to pull any image from that registry.
creamy-pencil-82913
03/27/2023, 6:25 AMYou'll need to use image pull secrets instead, and ensure that the correct credential secret is used to pull the image.
h
hallowed-breakfast-56871
03/27/2023, 6:27 AMOuch, OK.
I was trying to avoid managing lots of credentials between all the many namespaces.
hallowed-breakfast-56871
03/27/2023, 6:28 AMThanks for the information. 😉
31 Views