-
Task
-
Resolution: Done
-
Blocker
-
2.0.0.GA
-
None
We need to test installation of CRW 2.0 on OperatorHub. It requires having CRW 2.0 operator, which is linked to quay.io/crw image storage, instead of registry.redhat.io for the time we don't have CRW bit's on registry.redhat.io.
Existed CRW 2.0 operator application doesn't work with latest quay.io/crw/operator-rhel8:2.0-33 . It tries to pull server, devfile registry, plugin registry images from registry.redhat.io, while there is quay.io/crw in default.go file.
- is related to
-
CRW-380 publish operator application to quay as part of push-latest-containers-to-quay job
- Closed