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
After much head scratching I think I've worked out that registry-creds only adds imagePullSecrets to the default service account in each namespace.
We lock down our pods by specifying our own, more restrictive, service accounts, so we don't get the awsecr-cred automatically added and our pods fail to download their image.
Maybe it could be possible to add an annotation to a service account to get it included in registry-creds' sync?
In the meantime, I presume the best/only workaround is to explicitly add the imagePullSecrets entry to our own service account definition?
It would also be good to make this more explicit in the readme - I've just spent 2 days trying to work out why registry-creds didn't work for one of my pods when it worked for all my others.
The text was updated successfully, but these errors were encountered:
After much head scratching I think I've worked out that registry-creds only adds
imagePullSecrets
to the default service account in each namespace.We lock down our pods by specifying our own, more restrictive, service accounts, so we don't get the
awsecr-cred
automatically added and our pods fail to download their image.Maybe it could be possible to add an annotation to a service account to get it included in registry-creds' sync?
In the meantime, I presume the best/only workaround is to explicitly add the
imagePullSecrets
entry to our own service account definition?It would also be good to make this more explicit in the readme - I've just spent 2 days trying to work out why registry-creds didn't work for one of my pods when it worked for all my others.
The text was updated successfully, but these errors were encountered: