mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
79 lines
5.4 KiB
Plaintext
79 lines
5.4 KiB
Plaintext
:_mod-docs-content-type: ASSEMBLY
|
|
[id="olm-restricted-networks"]
|
|
= Using Operator Lifecycle Manager in disconnected environments
|
|
include::_attributes/common-attributes.adoc[]
|
|
:context: olm-restricted-networks
|
|
|
|
toc::[]
|
|
|
|
For {product-title} clusters in disconnected environments, Operator Lifecycle Manager (OLM) by default cannot access the Red{nbsp}Hat-provided software catalog sources hosted on remote registries because those remote sources require full internet connectivity.
|
|
|
|
However, as a cluster administrator you can still enable your cluster to use OLM in a disconnected environment if you have a workstation that has full internet access. The workstation, which requires full internet access to pull the remote software catalog content, is used to prepare local mirrors of the remote sources, and push the content to a mirror registry.
|
|
|
|
The mirror registry can be located on a bastion host, which requires connectivity to both your workstation and the disconnected cluster, or a completely disconnected, or _airgapped_, host, which requires removable media to physically move the mirrored content to the disconnected environment.
|
|
|
|
This guide describes the following process that is required to enable OLM in disconnected environments:
|
|
|
|
* Disable the default remote software catalog sources for OLM.
|
|
* Use a workstation with full internet access to create and push local mirrors of the software catalog content to a mirror registry.
|
|
* Configure OLM to install and manage Operators from local sources on the mirror registry instead of the default remote sources.
|
|
|
|
After enabling OLM in a disconnected environment, you can continue to use your unrestricted workstation to keep your local software catalog sources updated as newer versions of Operators are released.
|
|
|
|
[IMPORTANT]
|
|
====
|
|
While OLM can manage Operators from local sources, the ability for a given Operator to run successfully in a disconnected environment still depends on the Operator itself meeting the following criteria:
|
|
|
|
* List any related images, or other container images that the Operator might require to perform their functions, in the `relatedImages` parameter of its `ClusterServiceVersion` (CSV) object.
|
|
* Reference all specified images by a digest (SHA) and not by a tag.
|
|
|
|
You can search software on the link:https://catalog.redhat.com/software/search?p=1&deployed_as=Operator&type=Containerized%20application&badges_and_features=Disconnected[Red{nbsp}Hat Ecosystem Catalog] for a list of Red{nbsp}Hat Operators that support running in disconnected mode by filtering with the following selections:
|
|
|
|
[horizontal]
|
|
Type:: Containerized application
|
|
Deployment method:: Operator
|
|
Infrastructure features:: Disconnected
|
|
====
|
|
|
|
[role="_additional-resources"]
|
|
.Additional resources
|
|
|
|
* xref:../operators/understanding/olm-rh-catalogs.adoc#olm-rh-catalogs[Red{nbsp}Hat-provided Operator catalogs]
|
|
|
|
[id="olm-restricted-network-prereqs"]
|
|
== Prerequisites
|
|
|
|
* You are logged in to your {product-title} cluster as a user with `cluster-admin` privileges.
|
|
|
|
* If you are using OLM in a disconnected environment on {ibm-z-name}, you must have at least 12 GB allocated to the directory where you place your registry.
|
|
|
|
include::modules/olm-restricted-networks-configuring-operatorhub.adoc[leveloffset=+1]
|
|
|
|
[id="olm-mirror-catalog_olm-restricted-networks"]
|
|
== Mirroring an Operator catalog
|
|
|
|
For instructions about mirroring Operator catalogs for use with disconnected clusters, see xref:../disconnected/installing-mirroring-installation-images.adoc#olm-mirror-catalog_installing-mirroring-installation-images[Mirroring Operator catalogs for use with disconnected clusters].
|
|
|
|
[IMPORTANT]
|
|
====
|
|
As of {product-title} 4.11, the default Red{nbsp}Hat-provided Operator catalog releases in the file-based catalog format. The default Red{nbsp}Hat-provided Operator catalogs for {product-title} 4.6 through 4.10 released in the deprecated SQLite database format.
|
|
|
|
The `opm` subcommands, flags, and functionality related to the SQLite database format are also deprecated and will be removed in a future release. The features are still supported and must be used for catalogs that use the deprecated SQLite database format.
|
|
|
|
Many of the `opm` subcommands and flags for working with the SQLite database format, such as `opm index prune`, do not work with the file-based catalog format. For more information about working with file-based catalogs, see xref:../operators/understanding/olm-packaging-format.adoc#olm-file-based-catalogs_olm-packaging-format[Operator Framework packaging format], xref:../operators/admin/olm-managing-custom-catalogs.adoc#olm-managing-custom-catalogs-fb[Managing custom catalogs], and xref:../disconnected/about-installing-oc-mirror-v2.adoc#about-installing-oc-mirror-v2[Mirroring images for a disconnected installation by using the oc-mirror plugin v2].
|
|
====
|
|
|
|
include::modules/olm-creating-catalog-from-index.adoc[leveloffset=+1]
|
|
|
|
[role="_additional-resources"]
|
|
.Additional resources
|
|
|
|
* xref:../operators/admin/olm-managing-custom-catalogs.adoc#olm-accessing-images-private-registries_olm-managing-custom-catalogs[Accessing images for Operators from private registries]
|
|
* xref:../operators/understanding/olm/olm-understanding-olm.adoc#olm-catalogsource-image-template_olm-understanding-olm[Image template for custom catalog sources]
|
|
* xref:../openshift_images/managing_images/image-pull-policy.adoc#image-pull-policy[Image pull policy]
|
|
|
|
[id="next-steps_olm-restricted-networks"]
|
|
== Next steps
|
|
|
|
* xref:../operators/admin/olm-upgrading-operators.adoc#olm-upgrading-operators[Updating installed Operators]
|