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
Is your feature request related to a problem? Please describe.
A cluster may contain pods with images from a large number of private repos (e.g. multi-tenant clusters), where configuring version-checker for each private repo can be quite tedious/possibly a never ending activity.
Describe the solution you'd like
Given that pods running in a cluster that are sourced from private repos already have credentials provided, it should be possible to automatically discover the credentials using the pods image pull secrets.
Describe alternatives you've considered
Nothing really viable I can think of.
Additional context
Given that this requires access to Kubernetes secrets, it should be toggleable on/off in the chart as not everyone may want to grant read access to secrets (or need to). If this feature is accepted, it may also be worth considering supporting OpenShifts global image pull secret so that any registries configured there can be authenticated to. Again the idea is to make it automatic, so that credentials would not need to be copied to version-checkers helm values file for every private registry/repo.
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
A cluster may contain pods with images from a large number of private repos (e.g. multi-tenant clusters), where configuring version-checker for each private repo can be quite tedious/possibly a never ending activity.
Describe the solution you'd like
Given that pods running in a cluster that are sourced from private repos already have credentials provided, it should be possible to automatically discover the credentials using the pods image pull secrets.
Describe alternatives you've considered
Nothing really viable I can think of.
Additional context
Given that this requires access to Kubernetes secrets, it should be toggleable on/off in the chart as not everyone may want to grant read access to secrets (or need to). If this feature is accepted, it may also be worth considering supporting OpenShifts global image pull secret
so that any registries configured there can be authenticated to. Again the idea is to make it automatic, so that credentials would not need to be copied to version-checkers helm values file for every private registry/repo.
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: