Describe the feature you'd like to have
We currently can overwrite the images used by the various containers using the imageSet feature. However, we would like to rather have an ability to just overwrite the registry/repository path without defining the version ourselves. The goal here is that the operator picks the version and we pull through our internal mirror.
Who is the end user and what is the use case where this feature will be valuable?
This will benefit users who want to pull upstream images through their local mirror and might have a policy in place that forbids pulling from upstream mirrors.
How will we know we have a good solution? (acceptance criteria)
- Allow defining mirrors per upstream registry
- Allow using the operator defined versions, so that we do not have to maintain versions ourselves and just update the operator to get new image versions
Additional context
N/A
Describe the feature you'd like to have
We currently can overwrite the images used by the various containers using the imageSet feature. However, we would like to rather have an ability to just overwrite the registry/repository path without defining the version ourselves. The goal here is that the operator picks the version and we pull through our internal mirror.
Who is the end user and what is the use case where this feature will be valuable?
This will benefit users who want to pull upstream images through their local mirror and might have a policy in place that forbids pulling from upstream mirrors.
How will we know we have a good solution? (acceptance criteria)
Additional context
N/A