-
Task
-
Resolution: Done
-
Major
-
2.9.0.GA
-
None
-
False
-
False
-
Undefined
-
Based on Hosted Che call today, decisions are:
- today, continue to use KIPO to deploy Che KIP [resolve this issue as won't do]
- soon, deprecate Che KIP and set KIPO to deploy CRW KIP instead (we don't need both, and it's better to have the stable prod'tzed version) 19656
- in parallel, work on updating the KIPO and KIP so that it can be preloaded with the list of RELATED_IMAGES from the Che/CRW operator CSV, so that user experience is one click to enable the KIPO, rather than having to manually add the list of images to pull. 19657
- See also 18378 and 18570
Two things need to be verified here, once implemented in upstream (schedule TBD):
- CRW operator deploys KIPO community operator, which then installs CRW KIP image: https://github.com/eclipse/che/issues/19656
- KIP image can automatically pull CRW images w/o needing user input (preloaded from CRW operator CSV's RELATED_IMAGES_* env vars): https://github.com/eclipse/che/issues/19657
- relates to
-
CRW-1651 Automatically use productized version of k8s-image-puller, when imagePuller is specified in checluster CR
-
- Closed
-