-
Bug
-
Resolution: Unresolved
-
Normal
-
4.13, 4.12, 4.14, 4.15, 4.16, 4.17
-
Quality / Stability / Reliability
-
False
-
-
5
-
Moderate
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
"Converting a connected cluster to a disconnected cluster" is missing some procedure for CatalogSource.
When creating a disconnected cluster, we need to create CatalogSource resource as well as ImageContentSourcePolicy resource. (Ref [1])
However, "Converting a connected cluster to a disconnected cluster" documents is missing some steps for CatalogSource.
I think the document needs some additional steps like the following example after creating ImageContentSourcePolicy resource:
1. Create CatalogSource resource for your mirror repository according to the following document: https://docs.openshift.com/container-platform/4.16/operators/admin/olm-restricted-networks.html#olm-creating-catalog-from-index_olm-restricted-networks 2. Regarding the installed operators, update Subscription.spec.source to the new CatalogSource resource: # oc get subscription -A # oc edit subscription <subscription> -n <namespace> : spec: channel: stable-4.14 installPlanApproval: Automatic name: odf-operator source: redhat-operators <=============(*)change to the new CatalogSource resourcename sourceNamespace: openshift-marketplace : 3. Disable default CatalogSource resources according to the following document: https://docs.openshift.com/container-platform/4.16/operators/admin/olm-restricted-networks.html#olm-restricted-networks-operatorhub_olm-restricted-networks
"Restoring the network" section of the "Converting a connected cluster to a disconnected cluster" document is also missing some steps for CatalogSource.
Regarding restoring the network, we already have a similar KCS below.
I think the document can have the same content, or a link to the KCS.
- Converting a disconnected cluster to a connected cluster
https://access.redhat.com/solutions/6966995
Additionally, I think the "Converting a connected cluster to a disconnected cluster" document should have a statement at the beginning, which describes that there are some operators which doesn't support disconnected mode, so that we can prevent customers who are using operators which doesn't support disconnected mode from converting their clusters to disconnected.
I think the document can have a link to the following KCS:
- Red Hat Operators Supported in Disconnected Mode
https://access.redhat.com/articles/4740011
Affected Documents:
And all other versions
[1]https://docs.redhat.com/en/documentation/openshift_container_platform/4.17/html-single/disconnected_environments/index#oc-mirror-updating-cluster-manifests_installing-mirroring-disconnected