[chectl] Add workspace specific "RELATED_IMAGE" to the operator.yaml to make it consistent with csv #20005
Labels
area/che-operator
Issues and PRs related to Eclipse Che Kubernetes Operator
kind/enhancement
A feature request - must adhere to the feature request template.
severity/P1
Has a major impact to usage or development of the system.
Milestone
Is your enhancement related to a problem? Please describe.
Currently
RELATED_IMAGES_*
vary across installation methods:installer --olm
contain extended list of RELATED_IMAGES, including workspace specific - https://github.com/operator-framework/community-operators/blob/b560ec81cd4e586e9cb05c3674426da4971ba3b3/community-operators/eclipse-che/7.32.0/eclipse-che.v7.32.0.clusterserviceversion.yaml#L1029-L1142installer --operator
only contains basic (non workspace-specifc) list of images - https://github.com/eclipse-che/che-operator/blob/main/deploy/operator.yaml#L52-L81Since it is planned to fall back on the
RELATED_IMAGES_*
for the kubernetes image puller integration with Eclipse Che it would be great to have the extended list of images available as env vars regardless of the installation method. This issue is important for:Describe the solution you'd like
RELATED_IMAGES_*
are consistent across the installation methods - Operatorhub, chectl (operator), chectl(olm)Image puller is going to generate the images for pre-pulling based on the RELATED_IMAGES env var
Describe alternatives you've considered
N/A
Additional context
This issue is considered to be an important enhancement for the further kubernetes image puller integration with Eclipse Che:
The text was updated successfully, but these errors were encountered: