-
Bug
-
Resolution: Done
-
Undefined
-
None
-
None
-
2
-
False
-
-
False
-
As this is for unsupported CI builds, it should not be provided to end users and is not to be documented in the release notes.
-
Release Note Not Required
-
-
-
RHDH Core Team 3261, RHDH Core Team 3262, RHDH Install 3264
Today the approach to installing RHDH CI builds w/ operator requires an ICSP to be created in the cluster but some clusters don't support this even when you're logged in as admin... lookin' at you AWS, IBM Cloud.
So as a workaround for this, we could:
- extract the image references from the IIB
- convert those image refs to quay.io references
- pull those containers locally
- push them into your cluster using the registry-proxy URL reference
- THEN perform the catalog source installation step, which would find the registry-proxy image names within the local cluster, and no ICSP mapping would be needed.
Existing doc on how to pull images into an airgap:
- https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.2/html-single/administration_guide_for_red_hat_developer_hub/index#proc-install-rhdh-airgapped-environment-ocp-helm_assembly-install-rhdh-ocp and
- https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.2/html-single/administration_guide_for_red_hat_developer_hub/index#proc-install-rhdh-airgapped-environment-ocp-operator_assembly-install-rhdh-ocp
sample set of images as referenced in the CSV/IIB:
$➔ ~/pp/checkImagesInIIB.sh --digests -qq quay.io/rhdh/iib:1.2-v4.14-x86_64 registry-proxy.engineering.redhat.com/rh-osbs/rhdh-rhdh-operator-bundle@sha256:fe079e6ce4d08d300062b7c302ad15209b4984aeb3b4dcb7dcb73e29cdf75e81 registry.redhat.io/openshift4/ose-kube-rbac-proxy@sha256:55a49d79b9d29757328762e8a4755013fba1ead5a2416cc737e8b06dd2a77eef registry.redhat.io/rhdh/rhdh-hub-rhel9@sha256:3dda237c066787dd3e04df006a1ad7ce56eda8e8c89c31bfec0e7d115ed08f54 registry.redhat.io/rhdh/rhdh-rhel9-operator@sha256:1d7fa4a8e6f66d4bbd31fb8a8e910ddf69987c6cec50d83222cb4d6f39dae5e8 registry.redhat.io/rhel9/postgresql-15@sha256:5c4cad6de1b8e2537c845ef43b588a11347a3297bfab5ea611c032f866a1cb4e
sample set of images as found on the internet:
$➔ ~/pp/checkImagesInIIB.sh --digests --brew -qq quay.io/rhdh/iib:1.2-v4.14-x86_64 registry-proxy.engineering.redhat.com/rh-osbs/rhdh-rhdh-operator-bundle@sha256:fe079e6ce4d08d300062b7c302ad15209b4984aeb3b4dcb7dcb73e29cdf75e81 registry.redhat.io/openshift4/ose-kube-rbac-proxy@sha256:55a49d79b9d29757328762e8a4755013fba1ead5a2416cc737e8b06dd2a77eef brew.registry.redhat.io/rh-osbs/rhdh-rhdh-hub-rhel9@sha256:3dda237c066787dd3e04df006a1ad7ce56eda8e8c89c31bfec0e7d115ed08f54 brew.registry.redhat.io/rh-osbs/rhdh-rhdh-rhel9-operator@sha256:1d7fa4a8e6f66d4bbd31fb8a8e910ddf69987c6cec50d83222cb4d6f39dae5e8 registry.redhat.io/rhel9/postgresql-15@sha256:5c4cad6de1b8e2537c845ef43b588a11347a3297bfab5ea611c032f866a1cb4e or $➔ ~/pp/checkImagesInIIB.sh --digests --quay -qq quay.io/rhdh/iib:1.2-v4.14-x86_64 registry-proxy.engineering.redhat.com/rh-osbs/rhdh-rhdh-operator-bundle@sha256:fe079e6ce4d08d300062b7c302ad15209b4984aeb3b4dcb7dcb73e29cdf75e81 registry.redhat.io/openshift4/ose-kube-rbac-proxy@sha256:55a49d79b9d29757328762e8a4755013fba1ead5a2416cc737e8b06dd2a77eef quay.io/rhdh/rhdh-hub-rhel9@sha256:3dda237c066787dd3e04df006a1ad7ce56eda8e8c89c31bfec0e7d115ed08f54 quay.io/rhdh/rhdh-rhel9-operator@sha256:1d7fa4a8e6f66d4bbd31fb8a8e910ddf69987c6cec50d83222cb4d6f39dae5e8 registry.redhat.io/rhel9/postgresql-15@sha256:5c4cad6de1b8e2537c845ef43b588a11347a3297bfab5ea611c032f866a1cb4e
So we would need to pull those images using registry-proxy and brew.reg or quay.io paths, then push them into the cluster as registry-prox and reg.rh.io to get the correct mapping inside the cluster.
Script could live in
- https://github.com/redhat-developer/rhdh-operator/tree/main/.rhdh along with the other installation scripts and docs (for operator) and
- https://github.com/redhat-developer/rhdh-chart/tree/main/docs (if the script is significantly different)
- is related to
-
-
- Closed
-
- relates to
-
RHIDP-2814 Enable digest pinning in RHDH helm charts (as done in operator-bundle)
-
- Closed
-
