mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
Revert "Revert "OSDOCS-14501: Prune Operators""
This commit is contained in:
Eric Ponvelle
committed by
openshift-cherrypick-robot
openshift-cherrypick-robot
parent
c7ebbefb89
commit
63c63d2f40
@@ -11,12 +11,11 @@ toc::[]
|
||||
|
||||
Using Operator Lifecycle Manager (OLM),
|
||||
ifndef::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]
|
||||
cluster administrators
|
||||
cluster administrators can install OLM-based Operators to an {product-title} cluster.
|
||||
endif::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]
|
||||
ifdef::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]
|
||||
administrators with the `dedicated-admin` role
|
||||
administrators with the `dedicated-admin` role can install OLM-based Operators to a {product-title} cluster.
|
||||
endif::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]
|
||||
can install OLM-based Operators to an {product-title} cluster.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
|
||||
@@ -6,7 +6,7 @@ include::_attributes/common-attributes.adoc[]
|
||||
|
||||
toc::[]
|
||||
|
||||
If a global proxy is configured on the {product-title} cluster, Operator Lifecycle Manager (OLM) automatically configures Operators that it manages with the cluster-wide proxy. However, you can also configure installed Operators to override the global proxy or inject a custom CA certificate.
|
||||
If a global proxy is configured on your {product-title} cluster, Operator Lifecycle Manager (OLM) automatically configures Operators that it manages with the cluster-wide proxy. However, you can also configure installed Operators to override the global proxy or inject a custom CA certificate.
|
||||
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
@@ -15,9 +15,9 @@ If a global proxy is configured on the {product-title} cluster, Operator Lifecyc
|
||||
ifndef::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]
|
||||
* xref:../../networking/configuring_network_settings/enable-cluster-wide-proxy.adoc#enable-cluster-wide-proxy[Configuring the cluster-wide proxy]
|
||||
endif::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]
|
||||
ifdef::openshift-dedicated,openshift-rosa[]
|
||||
ifdef::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]
|
||||
* xref:../../networking/ovn_kubernetes_network_provider/configuring-cluster-wide-proxy.adoc#configuring-cluster-wide-proxy[Configuring a cluster-wide proxy]
|
||||
endif::openshift-dedicated,openshift-rosa[]
|
||||
endif::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]
|
||||
|
||||
// This xref points to a topic that is not currently included in the OSD and ROSA docs.
|
||||
ifndef::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]
|
||||
|
||||
@@ -16,7 +16,7 @@ As an administrator, you can override these values by modifying fields in the `C
|
||||
|
||||
[IMPORTANT]
|
||||
====
|
||||
The Marketplace Operator, `openshift-marketplace`, manages the default `OperatorHub` custom resource's (CR). This CR manages `CatalogSource` objects. If you attempt to modify fields in the `CatalogSource` object’s `spec.grpcPodConfig` section, the Marketplace Operator automatically reverts these modifications.By default, if you modify fields in the `spec.grpcPodConfig` section of the `CatalogSource` object, the Marketplace Operator automatically reverts these changes.
|
||||
The Marketplace Operator, `openshift-marketplace`, manages the default `OperatorHub` custom resource's (CR). This CR manages `CatalogSource` objects. If you attempt to modify fields in the `CatalogSource` object's `spec.grpcPodConfig` section, the Marketplace Operator automatically reverts these modifications. By default, if you modify fields in the `spec.grpcPodConfig` section of the `CatalogSource` object, the Marketplace Operator automatically reverts these changes.
|
||||
|
||||
To apply persistent changes to `CatalogSource` object, you must first disable a default `CatalogSource` object.
|
||||
====
|
||||
|
||||
@@ -86,10 +86,7 @@ include::modules/olm-catalog-source-and-psa.adoc[leveloffset=+1]
|
||||
[role="_additional-resources"]
|
||||
.Additional resources
|
||||
|
||||
// TODO-HCP remove conditions for HCP after cli_tools book is migrated
|
||||
ifndef::openshift-rosa-hcp[]
|
||||
* xref:../../authentication/understanding-and-managing-pod-security-admission.adoc#understanding-and-managing-pod-security-admission[Understanding and managing pod security admission]
|
||||
endif::openshift-rosa-hcp[]
|
||||
|
||||
include::modules/olm-migrating-sqlite-catalog-to-fbc.adoc[leveloffset=+2]
|
||||
|
||||
|
||||
@@ -6,7 +6,14 @@ include::_attributes/common-attributes.adoc[]
|
||||
|
||||
toc::[]
|
||||
|
||||
The default behavior for Operator Lifecycle Manager (OLM) aims to provide simplicity during Operator installation. However, this behavior can lack flexibility, especially in multitenant clusters. In order for multiple tenants on a {product-title} cluster to use an Operator, the default behavior of OLM requires that administrators install the Operator in *All namespaces* mode, which can be considered to violate the principle of least privilege.
|
||||
The default behavior for Operator Lifecycle Manager (OLM) aims to provide simplicity during Operator installation. However, this behavior can lack flexibility, especially in multitenant clusters. In order for multiple tenants on
|
||||
ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
|
||||
an {product-title}
|
||||
endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
|
||||
ifdef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
|
||||
a {product-title}
|
||||
endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
|
||||
cluster to use an Operator, the default behavior of OLM requires that administrators install the Operator in *All namespaces* mode, which can be considered to violate the principle of least privilege.
|
||||
|
||||
Consider the following scenarios to determine which Operator installation workflow works best for your environment and requirements.
|
||||
|
||||
|
||||
@@ -17,10 +17,8 @@ include::modules/olm-dependencies.adoc[leveloffset=+2]
|
||||
* xref:../../operators/understanding/olm/olm-understanding-dependency-resolution.adoc#olm-understanding-dependency-resolution[Operator Lifecycle Manager dependency resolution]
|
||||
|
||||
include::modules/olm-about-opm.adoc[leveloffset=+2]
|
||||
// TODO-HCP remove conditions for HCP after cli_tools book is migrated
|
||||
ifndef::openshift-rosa-hcp[]
|
||||
|
||||
* See xref:../../cli_reference/opm/cli-opm-install.adoc#cli-opm-install[CLI tools] for steps on installing the `opm` CLI.
|
||||
endif::openshift-rosa-hcp[]
|
||||
|
||||
ifdef::openshift-origin[]
|
||||
[id="olm-packaging-format-addtl-resources"]
|
||||
@@ -70,9 +68,7 @@ include::modules/olm-fb-catalogs-guidelines.adoc[leveloffset=+2]
|
||||
=== CLI usage
|
||||
|
||||
For instructions about creating file-based catalogs by using the `opm` CLI, see xref:../../operators/admin/olm-managing-custom-catalogs.adoc#olm-creating-fb-catalog-image_olm-managing-custom-catalogs[Managing custom catalogs].
|
||||
// TODO-HCP remove conditions for HCP after cli_tools book is migrated
|
||||
ifndef::openshift-rosa-hcp[]
|
||||
|
||||
For reference documentation about the `opm` CLI commands related to managing file-based catalogs, see xref:../../cli_reference/opm/cli-opm-ref.adoc#cli-opm-ref[CLI tools].
|
||||
endif::openshift-rosa-hcp[]
|
||||
|
||||
include::modules/olm-fb-catalogs-automation.adoc[leveloffset=+2]
|
||||
|
||||
Reference in New Issue
Block a user