1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-06 15:46:57 +01:00
Files
openshift-docs/disconnected/about.adoc
2025-01-29 16:43:33 -05:00

61 lines
3.7 KiB
Plaintext

:_mod-docs-content-type: ASSEMBLY
[id="about-disconnected-environments"]
= About disconnected environments
include::_attributes/common-attributes.adoc[]
:context: about-disconnected-environments
toc::[]
A disconnected environment is an environment that does not have full access to the internet.
{product-title} is designed to perform many automatic functions that depend on an internet connection, such as retrieving release images from a registry or retrieving update paths and recommendations for the cluster.
Without a direct internet connection, you must perform additional setup and configuration for your cluster to maintain full functionality in the disconnected environment.
[id="glossary-disconnected_{context}"]
== Glossary of disconnected environment terms
Although it is used throughout the {product-title} documentation, _disconnected environment_ is a broad term that can refer to environments with various levels of internet connectivity.
Other terms are sometimes used to refer to a specific level of internet connectivity, and these environments might require additional unique configurations.
The following table describes the different terms used to refer to environments without a full internet connection:
.Disconnected environment terms
[cols=".^2,.^4",options="header"]
|====
|Term |Description
|Air-gapped network
|An environment or network that is completely isolated from an external network.
This isolation depends on a physical separation, or an "air gap", between machines on the internal network and any other part of an external network.
Air-gapped environments are often used in industries with strict security or regulatory requirements.
|Disconnected environment
|An environment or network that has some level of isolation from an external network.
This isolation could be enabled by physical or logical separation between machines on the internal network and an external network.
Regardless of the level of isolation from the external network, a cluster in a disconnected environment does not have access to public services hosted by Red{nbsp}Hat and requires additional setup to maintain full cluster functionality.
|Restricted Network
|An environment or network with limited connection to an external network.
A physical connection may exist between machines on the internal network and an external network, but network traffic is limited by additional configurations, such as with firewalls and proxies.
|====
[id="preferred-methods_{context}"]
== Preferred methods for working with disconnected environments
// Not sure about the heading above, I'm trying to find some phrasing that basically says "You should probably use these things if you don't have a strong reason to go with other options".
You can choose between multiple options for most aspects of managing a cluster in a disconnected environment.
For example, when mirroring images you can choose between using the oc-mirror {oc-first} plugin or using the `oc adm` command.
However, some options provide a simpler and more convenient user experience for disconnected environments, and are the preferred method over their alternatives.
Unless your organizational needs require you to choose another option, use the following methods for mirroring images, installing your cluster, and updating your cluster:
* Mirror your images using the xref:../disconnected/mirroring/about-installing-oc-mirror-v2.adoc#about-installing-oc-mirror-v2[oc-mirror plugin v2].
* Install your cluster using the xref:../installing/installing_with_agent_based_installer/installing-with-agent-based-installer.adoc#installing-with-agent-based-installer[Agent-based Installer].
* Update your cluster using a xref:../disconnected/updating/disconnected-update-osus.adoc#updating-disconnected-cluster-osus[local OpenShift Update Service instance].