Merge pull request #54968 from bergerhoffer/updating-versions-for-ga

Updating versions from 4.11 to 4.12

Author: kalexand-rh

authentication/assuming-an-aws-iam-role-for-a-service-account.adoc

@@ -37,5 +37,5 @@ include::modules/verifying-the-assumed-iam-role-in-your-pod.adoc[leveloffset=+2]
 * For more information about installing and using the AWS Boto3 SDK for Python, see the link:https://boto3.amazonaws.com/v1/documentation/api/latest/index.html[AWS Boto3 documentation].
 
 ifdef::openshift-rosa,openshift-dedicated[]
-* For general information about webhook admission plugins for OpenShift, see link:https://docs.openshift.com/container-platform/4.11/architecture/admission-plug-ins.html#admission-webhooks-about_admission-plug-ins[Webhook admission plugins] in the OpenShift Container Platform documentation.
+* For general information about webhook admission plugins for OpenShift, see link:https://docs.openshift.com/container-platform/4.12/architecture/admission-plug-ins.html#admission-webhooks-about_admission-plug-ins[Webhook admission plugins] in the OpenShift Container Platform documentation.
 endif::openshift-rosa,openshift-dedicated[]

modules/about-developer-perspective.adoc

@@ -31,4 +31,4 @@ The *Developer* perspective provides workflows specific to developer use cases,
 You can use the *Topology* view to display applications, components, and workloads of your project. If you have no workloads in the project, the *Topology* view will show some links to create or import them. You can also use the *Quick Search* to import components directly.
 
 .Additional Resources
-See link:https://docs.openshift.com/container-platform/4.11/applications/odc-viewing-application-composition-using-topology-view.html[Viewing application composition using the Topology] view for more information on using the *Topology* view in *Developer* perspective.
+See link:https://docs.openshift.com/container-platform/4.12/applications/odc-viewing-application-composition-using-topology-view.html[Viewing application composition using the Topology] view for more information on using the *Topology* view in *Developer* perspective.

modules/ai-adding-worker-nodes-to-cluster.adoc

@@ -101,7 +101,7 @@ $ curl -s "$API_URL/api/assisted-install/v2/infra-envs/$INFRA_ENV_ID" -H "Author
 .Example output
 [source,terminal]
 ----
-https://api.openshift.com/api/assisted-images/images/41b91e72-c33e-42ee-b80f-b5c5bbf6431a?arch=x86_64&image_token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE2NTYwMjYzNzEsInN1YiI6IjQxYjkxZTcyLWMzM2UtNDJlZS1iODBmLWI1YzViYmY2NDMxYSJ9.1EX_VGaMNejMhrAvVRBS7PDPIQtbOOc8LtG8OukE1a4&type=minimal-iso&version=4.11
+https://api.openshift.com/api/assisted-images/images/41b91e72-c33e-42ee-b80f-b5c5bbf6431a?arch=x86_64&image_token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE2NTYwMjYzNzEsInN1YiI6IjQxYjkxZTcyLWMzM2UtNDJlZS1iODBmLWI1YzViYmY2NDMxYSJ9.1EX_VGaMNejMhrAvVRBS7PDPIQtbOOc8LtG8OukE1a4&type=minimal-iso&version=4.12
 ----
 
 . Download the ISO:

modules/architecture-machine-roles.adoc

@@ -14,9 +14,9 @@ The cluster also contains the definition for the `bootstrap` role. Because the b
 
 == Control plane and node host compatibility
 
-The {product-title} version must match between control plane host and node host. For example, in a 4.11 cluster, all control plane hosts must be 4.11 and all nodes must be 4.11.
+The {product-title} version must match between control plane host and node host. For example, in a 4.12 cluster, all control plane hosts must be 4.12 and all nodes must be 4.12.
 
-Temporary mismatches during cluster upgrades are acceptable. For example, when upgrading from {product-title} 4.10 to 4.11, some nodes will upgrade to 4.11 before others. Prolonged skewing of control plane hosts and node hosts might expose older compute machines to bugs and missing features. Users should resolve skewed control plane hosts and node hosts as soon as possible.
+Temporary mismatches during cluster upgrades are acceptable. For example, when upgrading from {product-title} 4.11 to 4.12, some nodes will upgrade to 4.12 before others. Prolonged skewing of control plane hosts and node hosts might expose older compute machines to bugs and missing features. Users should resolve skewed control plane hosts and node hosts as soon as possible.
 
 The `kubelet` service must not be newer than `kube-apiserver`, and can be up to two minor versions older depending on whether your {product-title} version is odd or even. The table below shows the appropriate version compatibility:
 
@@ -34,8 +34,8 @@ The `kubelet` service must not be newer than `kube-apiserver`, and can be up to
 |===
 [.small]
 --
-1. For example, {product-title} 4.5, 4.7, 4.9, 4.11.
-2. For example, {product-title} 4.6, 4.8, 4.10.
+1. For example, {product-title} 4.9, 4.11.
+2. For example, {product-title} 4.8, 4.10, 4.12.
 --
 
 [id="defining-workers_{context}"]
@@ -58,7 +58,7 @@ Compute machine sets are groupings of compute machine resources under the `machi
 [id="defining-masters_{context}"]
 == Cluster control planes
 
-In a Kubernetes cluster, the _master_ nodes run services that are required to control the Kubernetes cluster. In {product-title}, the control plane is comprised of control plane machines that have a `master` machine role. They contain more than just the Kubernetes services for managing the {product-title} cluster. 
+In a Kubernetes cluster, the _master_ nodes run services that are required to control the Kubernetes cluster. In {product-title}, the control plane is comprised of control plane machines that have a `master` machine role. They contain more than just the Kubernetes services for managing the {product-title} cluster.
 
 For most {product-title} clusters, control plane machines are defined by a series of standalone machine API resources. For supported cloud provider and {product-title} version combinations, control planes can be managed with control plane machine sets. Extra controls apply to control plane machines to prevent you from deleting all control plane machines and breaking your cluster.
 

modules/cli-installing-cli-rpm.adoc

@@ -46,7 +46,7 @@ For {op-system-base-full}, you can install the OpenShift CLI (`oc`) as an RPM if
 +
 [source,terminal]
 ----
-# subscription-manager repos --enable="rhocp-4.11-for-rhel-8-x86_64-rpms"
+# subscription-manager repos --enable="rhocp-4.12-for-rhel-8-x86_64-rpms"
 ----
 +
 [NOTE]

modules/cluster-logging-feature-reference.adoc

@@ -25,7 +25,7 @@ Vector does not support FIPS Enabled Clusters.
 
 .Prerequisites
 
-* {product-title}: 4.11
+* {product-title}: 4.12
 * {logging-title-uc}: 5.4
 * FIPS disabled
 

modules/cluster-logging-loki-tech-preview.adoc

@@ -20,7 +20,7 @@ You can use the {product-title} web console to install the LokiOperator.
 
 .Prerequisites
 
-* {product-title}: 4.11
+* {product-title}: 4.12
 * {logging-title-uc}: 5.4
 
 To install the LokiOperator using the {product-title} web console:

modules/cluster-logging-systemd-scaling.adoc

@@ -28,7 +28,7 @@ See "Creating machine configs with Butane" for information about Butane.
 [source,yaml]
 ----
 variant: openshift
-version: 4.11.0
+version: 4.12.0
 metadata:
   name: 40-worker-custom-journald
   labels:

modules/cluster-logging-vector-tech-preview.adoc

@@ -30,7 +30,7 @@ Vector does not support FIPS Enabled Clusters.
 
 .Prerequisites
 
-* {product-title}: 4.11
+* {product-title}: 4.12
 * {logging-title-uc}: 5.4
 * FIPS disabled
 

modules/cnf-provisioning-real-time-and-low-latency-workloads.adoc

@@ -366,7 +366,7 @@ annotations:
 [source,terminal]
 ----
 $ podman run --entrypoint performance-profile-creator -v \
-/must-gather:/must-gather:z registry.redhat.io/openshift4/performance-addon-rhel8-operator:v4.11 \
+/must-gather:/must-gather:z registry.redhat.io/openshift4/performance-addon-rhel8-operator:v4.12 \
 --mcp-name=worker-cnf --reserved-cpu-count=20 --rt-kernel=true \
 --split-reserved-cpus-across-numa=false --topology-manager-policy=single-numa-node \
 --must-gather-dir-path /must-gather -power-consumption-mode=low-latency \ <1>
@@ -440,4 +440,4 @@ spec:
   ...
 ----
 
-. Restart the pods.
+. Restart the pods.