openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

Fixing TechPreviewNoUpgrade typos

Browse Source
This commit is contained in:
Sebastian Kopacz
2024-05-31 11:18:10 -04:00
committed by openshift-cherrypick-robot
parent 523b616ffa
commit e5ccbddace
5 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
modules/arch-platform-operators.adoc
View File

@@ -22,4 +22,4 @@ Operator Lifecycle Manager (OLM) introduces a new type of Operator called _platf
Using the existing cluster capabilities feature in {product-title}, cluster administrators can already disable a subset of Cluster Version Operator-based (CVO) components considered non-essential to the initial payload prior to cluster installation. Platform Operators iterate on this model by providing additional customization options. Through the platform Operator mechanism, which relies on resources from the RukPak component, OLM-based Operators can now be installed at cluster installation time and can block cluster rollout if the Operator fails to install successfully.
In {product-title} 4.12, this Technology Preview release focuses on the basic platform Operator mechanism and builds a foundation for expanding the concept in upcoming releases. You can use the cluster-wide `PlatformOperator` API to configure Operators before or after cluster creation on clusters that have enabled the `TechPreviewNoUpgrades` feature set.
In {product-title} 4.12, this Technology Preview release focuses on the basic platform Operator mechanism and builds a foundation for expanding the concept in upcoming releases. You can use the cluster-wide `PlatformOperator` API to configure Operators before or after cluster creation on clusters that have enabled the `TechPreviewNoUpgrade` feature set.

4
modules/olm-installing-po-after.adoc
View File

@@ -6,7 +6,7 @@
[id="olm-installing-po-after_{context}"]
= Installing platform Operators after cluster creation
As a cluster administrator, you can install platform Operators after cluster creation on clusters that have enabled the `TechPreviewNoUpgrades` feature set by using the cluster-wide `PlatformOperator` API.
As a cluster administrator, you can install platform Operators after cluster creation on clusters that have enabled the `TechPreviewNoUpgrade` feature set by using the cluster-wide `PlatformOperator` API.
.Procedure
@@ -35,7 +35,7 @@ $ oc apply -f service-mesh-po.yaml
+
[NOTE]
====
If your cluster does not have the `TechPreviewNoUpgrades` feature set enabled, the object creation fails with the following message:
If your cluster does not have the `TechPreviewNoUpgrade` feature set enabled, the object creation fails with the following message:
[source,terminal]
----

2
operators/admin/olm-managing-po.adoc
View File

@@ -24,7 +24,7 @@ include::modules/olm-po-techpreview.adoc[leveloffset=+2]
== Prerequisites
- Access to an {product-title} cluster using an account with `cluster-admin` permissions.
- The `TechPreviewNoUpgrades` feature set enabled on the cluster.
- The `TechPreviewNoUpgrade` feature set enabled on the cluster.
+
[WARNING]
====

2
operators/olm_v1/olmv1-installing-an-operator-from-a-catalog.adoc
View File

@@ -21,7 +21,7 @@ include::snippets/technology-preview.adoc[]
--
include::snippets/olmv1-cli-only.adoc[]
--
* The `TechPreviewNoUpgrades` feature set enabled on the cluster
* The `TechPreviewNoUpgrade` feature set enabled on the cluster
+
[WARNING]
====

2
operators/olm_v1/olmv1-managing-plain-bundles.adoc
View File

@@ -35,7 +35,7 @@ As a cluster administrator, you can build and publish a file-based catalog that
--
include::snippets/olmv1-cli-only.adoc[]
--
* The `TechPreviewNoUpgrades` feature set enabled on the cluster
* The `TechPreviewNoUpgrade` feature set enabled on the cluster
+
[WARNING]
====