mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
OSDOCS-16338: fixes cluster mentions MicroShift
This commit is contained in:
“Shauna Diaz”
committed by
openshift-cherrypick-robot
openshift-cherrypick-robot
parent
bd98da653c
commit
4a0bd7b8b1
@@ -1,6 +1,6 @@
|
||||
:_mod-docs-content-type: ASSEMBLY
|
||||
[id="microshift-operators-oc-mirror-disconnected"]
|
||||
= Adding OLM-based Operators to a disconnected cluster
|
||||
= Adding OLM-based Operators to a disconnected node
|
||||
include::_attributes/attributes-microshift.adoc[]
|
||||
:context: microshift-operators-oc-mirror-disconnected
|
||||
|
||||
|
||||
@@ -28,8 +28,8 @@ include::modules/microshift-oc-mirror-to-mirror.adoc[leveloffset=+1]
|
||||
//Convert the imageset file and add configuration to CRI-O
|
||||
include::modules/microshift-oc-mirror-transform-imageset-to-crio.adoc[leveloffset=+1]
|
||||
|
||||
//Apply changes to cluster so it can use Operators
|
||||
include::modules/microshift-oc-mirror-install-catalog-cluster.adoc[leveloffset=+1]
|
||||
//Apply changes to node so it can use Operators
|
||||
include::modules/microshift-oc-mirror-install-catalog-node.adoc[leveloffset=+1]
|
||||
|
||||
[id="Additional-resources_microshift-operators-oc-mirror_{context}"]
|
||||
[role="_additional-resources"]
|
||||
|
||||
@@ -15,10 +15,10 @@ Operator Lifecycle Manager (OLM) is used in {microshift-short} for installing an
|
||||
|
||||
* Cluster Operators as applied in {ocp} are not used in {microshift-short}.
|
||||
* You must create your own catalogs for the add-on Operators you want to use with your applications. Catalogs are not provided by default.
|
||||
** Each catalog must have an accessible `CatalogSource` added to a cluster, so that the OLM catalog Operator can use the catalog for content.
|
||||
* You must use the CLI to conduct OLM activities with {microshift-short}. The console, software catalog, and catalog management GUIs are not available.
|
||||
** Use the link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/cli_tools/opm-cli#cli-opm-install[Operator Package Manager `opm` CLI] with network-connected clusters, or for building catalogs for custom Operators that use an internal registry.
|
||||
** To mirror your catalogs and Operators for disconnected or offline clusters, install link:https://docs.openshift.com/container-platform/{ocp-version}/installing/disconnected_install/installing-mirroring-disconnected.html#installation-oc-mirror-installing-plugin_installing-mirroring-disconnected[the oc-mirror OpenShift CLI plugin].
|
||||
** Each catalog must have an accessible `CatalogSource` added to a node, so that the OLM catalog Operator can use the catalog for content.
|
||||
* You must use the CLI to conduct OLM activities with {microshift-short}. The console and OperatorHub GUIs are not available.
|
||||
** Use the link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/cli_tools/opm-cli#cli-opm-install[Operator Package Manager `opm` CLI] with a network-connected node, or for building catalogs for custom Operators that use an internal registry.
|
||||
** To mirror your catalogs and Operators for disconnected or offline nodes, install link:https://docs.openshift.com/container-platform/{ocp-version}/installing/disconnected_install/installing-mirroring-disconnected.html#installation-oc-mirror-installing-plugin_installing-mirroring-disconnected[the oc-mirror OpenShift CLI plugin].
|
||||
|
||||
[IMPORTANT]
|
||||
====
|
||||
@@ -27,7 +27,7 @@ Before using an Operator, verify with the provider that the Operator is supporte
|
||||
|
||||
[id="microshift-installing-olm-options_{context}"]
|
||||
== Determining your OLM installation type
|
||||
You can install the OLM package manager for use with {microshift-short} 4.15 or newer versions. There are different ways to install OLM for {microshift-short} clusters, depending on your use case.
|
||||
You can install the OLM package manager for use with {microshift-short} 4.15 or newer versions. There are different ways to install OLM for a {microshift-short} node, depending on your use case.
|
||||
|
||||
* You can install the `microshift-olm` RPM at the same time you install the {microshift-short} RPM on {op-system-base-full}.
|
||||
* You can install the `microshift-olm` on an existing {microshift-short} {product-version}. Restart the {microshift-short} service after installing OLM for the changes to apply.
|
||||
@@ -59,5 +59,5 @@ include::modules/microshift-olm-deploy-ops-spec-ns.adoc[leveloffset=+2]
|
||||
//additional resources for working with operators after deployment
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/operators/administrator-tasks#olm-upgrading-operators[Updating installed Operators]
|
||||
* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/operators/administrator-tasks#olm-deleting-operator-from-a-cluster-using-cli_olm-deleting-operators-from-a-cluster[Deleting Operators from a cluster using the CLI]
|
||||
* link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html/operators/administrator-tasks#olm-upgrading-operators[Updating installed Operators]
|
||||
* link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html/operators/administrator-tasks#olm-deleting-operator-from-a-cluster-using-cli_olm-deleting-operators-from-a-cluster[Deleting Operators from a cluster using the CLI]
|
||||
|
||||
@@ -6,16 +6,16 @@ include::_attributes/attributes-microshift.adoc[]
|
||||
|
||||
toc::[]
|
||||
|
||||
You can use Operators with {microshift-short} to create applications that monitor the running services in your cluster. Operators can manage applications and their resources, such as deploying a database or message bus. As customized software running inside your cluster, Operators can be used to implement and automate common operations.
|
||||
You can use Operators with {microshift-short} to create applications that monitor the running services in your node. Operators can manage applications and their resources, such as deploying a database or message bus. As customized software running inside your node, Operators can be used to implement and automate common operations.
|
||||
|
||||
Operators offer a more localized configuration experience and integrate with Kubernetes APIs and CLI tools such as `kubectl` and `oc`. Operators are designed specifically for your applications. Operators enable you to configure components instead of modifying a global configuration file.
|
||||
|
||||
{microshift-short} applications are generally expected to be deployed in static environments. However, Operators are available if helpful in your use case. To determine the compatibility of an Operator with {microshift-short}, check the Operator documentation.
|
||||
|
||||
[id="microshift-operators-installation-paths_{context}"]
|
||||
== How to use Operators with {microshift-short} clusters
|
||||
== How to use Operators with a {microshift-short} node
|
||||
|
||||
There are two ways to use Operators for your {microshift-short} clusters:
|
||||
There are two ways to use Operators for your {microshift-short} node:
|
||||
|
||||
[id="microshift-operators-paths-manifests_{context}"]
|
||||
=== Manifests for Operators
|
||||
@@ -25,6 +25,6 @@ Operators can be installed and managed directly by using manifests. You can use
|
||||
|
||||
[id="microshift-operators-paths-olm_{context}"]
|
||||
=== Operator Lifecycle Manager for Operators
|
||||
You can also install add-on Operators to a {microshift-short} cluster using Operator Lifecycle Manager (OLM). OLM can be used to manage both custom Operators and Operators that are widely available. Building catalogs is required to use OLM with {microshift-short}.
|
||||
You can also install add-on Operators to a {microshift-short} node by using Operator Lifecycle Manager (OLM). OLM can be used to manage both custom Operators and Operators that are widely available. Building catalogs is required to use OLM with {microshift-short}.
|
||||
|
||||
* For details, see xref:../../microshift_running_apps/microshift_operators/microshift-operators-olm.adoc#microshift-operators-olm[Using Operator Lifecycle Manager with {microshift-short}].
|
||||
|
||||
Reference in New Issue
Block a user