Problem/Justification
It’s too burdensome to use private registries with password protection
Impact
It would save a lot of time for those of us with private registries that have passwords so we don’t have to enter the same info over and over. This may be even more true with Electric Eel.
User Story
When using a custom app to pull an image from a public registry, I can use image pull policies of only pull images if not present on host and when an update comes, it can be pulled.
When using a custom app with a private registry, that will fail as user and password are not known. So, one has to use never pull image as the pull policy. And then, manually pull an image so they can type in the user/password, and, then, delete the old images if desired to clean up. And if you have say 20 custom apps being pulled from the same private registry, you have to manually pull all 20 images and specify the user and password 20 times as it is not retained.
Would it be much nicer for those who do they own deployments of custom apps to be able to specify the image repo user and password once and it be retained? By doing so, updates can be done more easily.
Even if you cannot for some reason save for system wide across multiple custom apps, if you could just retain it for each app, so, it only has to be done once ever.