mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
67 lines
3.6 KiB
Plaintext
67 lines
3.6 KiB
Plaintext
:_mod-docs-content-type: ASSEMBLY
|
|
[id="connected-to-disconnected"]
|
|
= Converting a connected cluster to a disconnected cluster
|
|
include::_attributes/common-attributes.adoc[]
|
|
:context: connected-to-disconnected
|
|
|
|
toc::[]
|
|
|
|
|
|
There might be some scenarios where you need to convert your {product-title} cluster from a connected cluster to a disconnected cluster.
|
|
|
|
A disconnected cluster, also known as a restricted cluster, does not have an active connection to the internet. As such, you must mirror the contents of your registries and installation media. You can create this mirror registry on a host that can access both the internet and your closed network, or copy images to a device that you can move across network boundaries.
|
|
|
|
This topic describes the general process for converting an existing, connected cluster into a disconnected cluster.
|
|
|
|
include::modules/installation-about-mirror-registry.adoc[leveloffset=+1]
|
|
|
|
[id="prerequisites_connected-to-disconnected_{context}"]
|
|
== Prerequisites
|
|
|
|
* The `oc` client is installed.
|
|
|
|
* A running cluster.
|
|
|
|
* An installed mirror registry, which is a container image registry that supports link:https://docs.docker.com/registry/spec/manifest-v2-2/[Docker v2-2] in the location that will host the {product-title} cluster, such as one of the following registries:
|
|
+
|
|
--
|
|
** link:https://www.redhat.com/en/technologies/cloud-computing/quay[Red{nbsp}Hat Quay]
|
|
|
|
** link:https://jfrog.com/artifactory/[JFrog Artifactory]
|
|
|
|
** link:https://www.sonatype.com/products/repository-oss?topnav=true[Sonatype Nexus Repository]
|
|
|
|
** link:https://goharbor.io/[Harbor]
|
|
--
|
|
+
|
|
If you have a subscription to Red{nbsp}Hat Quay, see the documentation on deploying Red{nbsp}Hat Quay link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html/deploy_red_hat_quay_for_proof-of-concept_non-production_purposes/[for proof-of-concept purposes] or link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html/deploying_the_red_hat_quay_operator_on_openshift_container_platform/index[by using the Quay Operator].
|
|
|
|
* The mirror repository must be configured to share images. For example, a {quay} repository requires link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/use_red_hat_quay/index#user-org-intro_use-quay[Organizations] in order to share images.
|
|
|
|
* Access to the internet to obtain the necessary container images.
|
|
|
|
include::modules/connected-to-disconnected-prepare-mirror.adoc[leveloffset=+1]
|
|
|
|
include::modules/connected-to-disconnected-mirror-images.adoc[leveloffset=+1]
|
|
|
|
[role="_additional-resources"]
|
|
.Additional resources
|
|
|
|
* For more information about mirroring Operator catalogs, see xref:../disconnected/using-olm.adoc#olm-mirror-catalog_olm-restricted-networks[Mirroring an Operator catalog].
|
|
* For more information about the `oc adm catalog mirror` command, see the xref:../cli_reference/openshift_cli/administrator-cli-commands.adoc#oc-adm-catalog-mirror[OpenShift CLI administrator command reference].
|
|
|
|
include::modules/connected-to-disconnected-config-registry.adoc[leveloffset=+1]
|
|
|
|
include::modules/connected-to-disconnected-verify.adoc[leveloffset=+1]
|
|
|
|
include::modules/connected-to-disconnected-disconnect.adoc[leveloffset=+1]
|
|
|
|
[NOTE]
|
|
====
|
|
The {insights-operator} is degraded when the cluster loses its Internet connection. You can avoid this problem by temporarily xref:../support/remote_health_monitoring/remote-health-reporting.adoc#insights-operator-new-pull-secret-disabled_remote-health-reporting[disabling the {insights-operator}] until you can restore it.
|
|
====
|
|
|
|
include::modules/connected-to-disconnected-restore-insights.adoc[leveloffset=+1]
|
|
|
|
include::modules/connected-to-disconnected-restore.adoc[leveloffset=+1]
|