diff --git a/authentication/assuming-an-aws-iam-role-for-a-service-account.adoc b/authentication/assuming-an-aws-iam-role-for-a-service-account.adoc index 3bf9575d03..80c43b7cb1 100644 --- a/authentication/assuming-an-aws-iam-role-for-a-service-account.adoc +++ b/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.12/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.13/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[] diff --git a/microshift_storage/understanding-persistent-storage-microshift.adoc b/microshift_storage/understanding-persistent-storage-microshift.adoc index 2fcb4d19c5..136e25ba85 100644 --- a/microshift_storage/understanding-persistent-storage-microshift.adoc +++ b/microshift_storage/understanding-persistent-storage-microshift.adoc @@ -13,7 +13,7 @@ include::modules/storage-persistent-storage-overview.adoc[leveloffset=+1] [id="additional-resources_understanding-persistent-storage-microshift"] [role="_additional-resources"] .Additional resources -* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.12/html/storage/understanding-persistent-storage#pv-access-modes_understanding-persistent-storage[Access modes for persistent storage] +* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.13/html/storage/understanding-persistent-storage#pv-access-modes_understanding-persistent-storage[Access modes for persistent storage] include::modules/storage-persistent-storage-lifecycle.adoc[leveloffset=+1] diff --git a/modules/about-developer-perspective.adoc b/modules/about-developer-perspective.adoc index c424135252..6566e4d23d 100644 --- a/modules/about-developer-perspective.adoc +++ b/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.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. +See link:https://docs.openshift.com/container-platform/4.13/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. diff --git a/modules/ai-adding-worker-nodes-to-cluster.adoc b/modules/ai-adding-worker-nodes-to-cluster.adoc index 6397036c2c..3e2f158939 100644 --- a/modules/ai-adding-worker-nodes-to-cluster.adoc +++ b/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.12 +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.13 ---- . Download the ISO: diff --git a/modules/architecture-machine-roles.adoc b/modules/architecture-machine-roles.adoc index 9741e47ecc..b7e497484b 100644 --- a/modules/architecture-machine-roles.adoc +++ b/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.12 cluster, all control plane hosts must be 4.12 and all nodes must be 4.12. +The {product-title} version must match between control plane host and node host. For example, in a 4.13 cluster, all control plane hosts must be 4.13 and all nodes must be 4.13. -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. +Temporary mismatches during cluster upgrades are acceptable. For example, when upgrading from {product-title} 4.12 to 4.13, some nodes will upgrade to 4.13 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.9, 4.11. -2. For example, {product-title} 4.8, 4.10, 4.12. +1. For example, {product-title} 4.11, 4.13. +2. For example, {product-title} 4.10, 4.12. -- [id="defining-workers_{context}"] diff --git a/modules/cli-installing-cli-rpm.adoc b/modules/cli-installing-cli-rpm.adoc index a0067d2b72..ecedb5b9bb 100644 --- a/modules/cli-installing-cli-rpm.adoc +++ b/modules/cli-installing-cli-rpm.adoc @@ -47,7 +47,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.12-for-rhel-8-x86_64-rpms" +# subscription-manager repos --enable="rhocp-4.13-for-rhel-8-x86_64-rpms" ---- + [NOTE] diff --git a/modules/cluster-logging-feature-reference.adoc b/modules/cluster-logging-feature-reference.adoc index ea7c79a385..2629a2dab5 100644 --- a/modules/cluster-logging-feature-reference.adoc +++ b/modules/cluster-logging-feature-reference.adoc @@ -25,7 +25,7 @@ Vector does not support FIPS Enabled Clusters. .Prerequisites -* {product-title}: 4.12 +* {product-title}: 4.13 * {logging-title-uc}: 5.4 * FIPS disabled diff --git a/modules/cluster-logging-loki-tech-preview.adoc b/modules/cluster-logging-loki-tech-preview.adoc index 977e58a138..9ec3560ebf 100644 --- a/modules/cluster-logging-loki-tech-preview.adoc +++ b/modules/cluster-logging-loki-tech-preview.adoc @@ -20,7 +20,7 @@ You can use the {product-title} web console to install the Loki Operator. .Prerequisites -* {product-title}: 4.12 +* {product-title}: 4.13 * {logging-title-uc}: 5.4 To install the Loki Operator using the {product-title} web console: diff --git a/modules/cluster-logging-systemd-scaling.adoc b/modules/cluster-logging-systemd-scaling.adoc index ac4d2f0a81..aeb747e0d5 100644 --- a/modules/cluster-logging-systemd-scaling.adoc +++ b/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.12.0 +version: 4.13.0 metadata: name: 40-worker-custom-journald labels: diff --git a/modules/cluster-logging-vector-tech-preview.adoc b/modules/cluster-logging-vector-tech-preview.adoc index ab260d16b5..1e69a31af7 100644 --- a/modules/cluster-logging-vector-tech-preview.adoc +++ b/modules/cluster-logging-vector-tech-preview.adoc @@ -30,7 +30,7 @@ Vector does not support FIPS Enabled Clusters. .Prerequisites -* {product-title}: 4.12 +* {product-title}: 4.13 * {logging-title-uc}: 5.4 * FIPS disabled diff --git a/modules/cnf-provisioning-real-time-and-low-latency-workloads.adoc b/modules/cnf-provisioning-real-time-and-low-latency-workloads.adoc index a2c9be2957..b284da1e62 100644 --- a/modules/cnf-provisioning-real-time-and-low-latency-workloads.adoc +++ b/modules/cnf-provisioning-real-time-and-low-latency-workloads.adoc @@ -371,7 +371,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.12 \ +/must-gather:/must-gather:z registry.redhat.io/openshift4/performance-addon-rhel8-operator:v4.13 \ --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> diff --git a/modules/configmap-removing-ca.adoc b/modules/configmap-removing-ca.adoc index e2ca776c58..a1bbe65d08 100644 --- a/modules/configmap-removing-ca.adoc +++ b/modules/configmap-removing-ca.adoc @@ -46,7 +46,7 @@ Before removal, the Additional trust bundle section appears, redacting its value Name: ID: External ID: -OpenShift Version: 4.12.0 +OpenShift Version: 4.13.0 Channel Group: stable DNS: AWS Account: @@ -76,7 +76,7 @@ After removing the proxy, the Additional trust bundle section is removed: Name: ID: External ID: -OpenShift Version: 4.12.0 +OpenShift Version: 4.13.0 Channel Group: stable DNS: AWS Account: diff --git a/modules/containers-signature-verify-enable.adoc b/modules/containers-signature-verify-enable.adoc index bdf3effb69..e9949a5acd 100644 --- a/modules/containers-signature-verify-enable.adoc +++ b/modules/containers-signature-verify-enable.adoc @@ -19,7 +19,7 @@ See "Creating machine configs with Butane" for information about Butane. [source,yaml] ---- variant: openshift -version: 4.12.0 +version: 4.13.0 metadata: name: 51-worker-rh-registry-trust labels: diff --git a/modules/coreos-layering-configuring.adoc b/modules/coreos-layering-configuring.adoc index fe051a8ff9..9f6e8930b9 100644 --- a/modules/coreos-layering-configuring.adoc +++ b/modules/coreos-layering-configuring.adoc @@ -24,7 +24,7 @@ When you configure a custom layered image, {product-title} no longer automatical You should use the same base {op-system} image that is installed on the rest of your cluster. Use the `oc adm release info --image-for rhel-coreos-8` command to obtain the base image being used in your cluster. ==== + -For example, the following Containerfile creates a custom layered image from an {product-title} 4.12 image and a Hotfix package: +For example, the following Containerfile creates a custom layered image from an {product-title} 4.13 image and a Hotfix package: + .Example Containerfile for a custom layer image [source,yaml] @@ -127,7 +127,7 @@ Name: rendered-master-4e8be63aef68b843b546827b6ebe0913 Namespace: Labels: Annotations: machineconfiguration.openshift.io/generated-by-controller-version: 8276d9c1f574481043d3661a1ace1f36cd8c3b62 - machineconfiguration.openshift.io/release-image-version: 4.12.0-ec.3 + machineconfiguration.openshift.io/release-image-version: 4.13.0-ec.3 API Version: machineconfiguration.openshift.io/v1 Kind: MachineConfig ... diff --git a/modules/creating-custom-live-rhcos-iso.adoc b/modules/creating-custom-live-rhcos-iso.adoc index de00b216fb..cd977df9af 100644 --- a/modules/creating-custom-live-rhcos-iso.adoc +++ b/modules/creating-custom-live-rhcos-iso.adoc @@ -69,11 +69,11 @@ The modified `sshd_config` file overrides the default `sshd_config` file. $ butane -p embedded.yaml -d files-dir/ > embedded.ign ---- -. Once the Ignition file is created, you can include the configuration in a new live {op-system} ISO, which is named `rhcos-sshd-4.12.0-x86_64-live.x86_64.iso`, with the `coreos-installer` utility: +. Once the Ignition file is created, you can include the configuration in a new live {op-system} ISO, which is named `rhcos-sshd-4.13.0-x86_64-live.x86_64.iso`, with the `coreos-installer` utility: + [source,terminal] ---- -$ coreos-installer iso ignition embed -i embedded.ign rhcos-4.12.0-x86_64-live.x86_64.iso -o rhcos-sshd-4.12.0-x86_64-live.x86_64.iso +$ coreos-installer iso ignition embed -i embedded.ign rhcos-4.13.0-x86_64-live.x86_64.iso -o rhcos-sshd-4.13.0-x86_64-live.x86_64.iso ---- .Verification @@ -82,7 +82,7 @@ $ coreos-installer iso ignition embed -i embedded.ign rhcos-4.12.0-x86_64-live.x + [source,terminal] ---- -# coreos-installer iso ignition show rhcos-sshd-4.12.0-x86_64-live.x86_64.iso +# coreos-installer iso ignition show rhcos-sshd-4.13.0-x86_64-live.x86_64.iso ---- + diff --git a/modules/customizing-the-jenkins-image-stream-tag.adoc b/modules/customizing-the-jenkins-image-stream-tag.adoc index 7686145f9b..18e44e51c5 100644 --- a/modules/customizing-the-jenkins-image-stream-tag.adoc +++ b/modules/customizing-the-jenkins-image-stream-tag.adoc @@ -23,7 +23,7 @@ To override the current upgrade value for existing deployments, change the value .Prerequisites -* You are running OpenShift Jenkins on {product-title} 4.12. +* You are running OpenShift Jenkins on {product-title} 4.13. * You know the namespace where OpenShift Jenkins is deployed. .Procedure diff --git a/modules/developer-cli-odo-installing-odo-on-linux-rpm.adoc b/modules/developer-cli-odo-installing-odo-on-linux-rpm.adoc index bb0fa59382..73dcde59a2 100644 --- a/modules/developer-cli-odo-installing-odo-on-linux-rpm.adoc +++ b/modules/developer-cli-odo-installing-odo-on-linux-rpm.adoc @@ -39,7 +39,7 @@ For {op-system-base-full}, you can install the `{odo-title}` CLI as an RPM. + [source,terminal] ---- -# subscription-manager repos --enable="ocp-tools-4.12-for-rhel-8-x86_64-rpms" +# subscription-manager repos --enable="ocp-tools-4.13-for-rhel-8-x86_64-rpms" ---- . Install the `{odo-title}` package: diff --git a/modules/eco-node-maintenance-operator-installation-cli.adoc b/modules/eco-node-maintenance-operator-installation-cli.adoc index 5411adab2c..1bdf3016f1 100644 --- a/modules/eco-node-maintenance-operator-installation-cli.adoc +++ b/modules/eco-node-maintenance-operator-installation-cli.adoc @@ -102,7 +102,7 @@ $ oc get csv -n openshift-operators [source,terminal] ---- NAME DISPLAY VERSION REPLACES PHASE -node-maintenance-operator.v4.12 Node Maintenance Operator 4.12 Succeeded +node-maintenance-operator.v4.13 Node Maintenance Operator 4.13 Succeeded ---- . Verify that the Node Maintenance Operator is running: + diff --git a/modules/enabling-baseline-capability-set.adoc b/modules/enabling-baseline-capability-set.adoc index cb0d500f15..711ad6fefe 100644 --- a/modules/enabling-baseline-capability-set.adoc +++ b/modules/enabling-baseline-capability-set.adoc @@ -20,6 +20,6 @@ As a cluster administrator, you can enable the capabilities by setting `baseline $ oc patch clusterversion version --type merge -p '{"spec":{"capabilities":{"baselineCapabilitySet":"vCurrent"}}}' <1> ---- + -<1> For `baselineCapabilitySet` you can specify `vCurrent`, `v4.11`, `v4.12`, or `None`. +<1> For `baselineCapabilitySet` you can specify `vCurrent`, `v4.12`, `v4.13`, or `None`. include::snippets/capabilities-table.adoc[] diff --git a/modules/graceful-restart.adoc b/modules/graceful-restart.adoc index 7c7999a992..e6c2282f97 100644 --- a/modules/graceful-restart.adoc +++ b/modules/graceful-restart.adoc @@ -119,14 +119,14 @@ Check that there are no cluster Operators with the `DEGRADED` condition set to ` [source,terminal] ---- NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE -authentication 4.12.0 True False False 59m -cloud-credential 4.12.0 True False False 85m -cluster-autoscaler 4.12.0 True False False 73m -config-operator 4.12.0 True False False 73m -console 4.12.0 True False False 62m -csi-snapshot-controller 4.12.0 True False False 66m -dns 4.12.0 True False False 76m -etcd 4.12.0 True False False 76m +authentication 4.13.0 True False False 59m +cloud-credential 4.13.0 True False False 85m +cluster-autoscaler 4.13.0 True False False 73m +config-operator 4.13.0 True False False 73m +console 4.13.0 True False False 62m +csi-snapshot-controller 4.13.0 True False False 66m +dns 4.13.0 True False False 76m +etcd 4.13.0 True False False 76m ... ---- diff --git a/modules/insights-operator-one-time-gather.adoc b/modules/insights-operator-one-time-gather.adoc index 69c39f630b..0ca11957ad 100644 --- a/modules/insights-operator-one-time-gather.adoc +++ b/modules/insights-operator-one-time-gather.adoc @@ -20,7 +20,7 @@ You must run a gather operation to create an Insights Operator archive. + [source,yaml] ---- -include::https://raw.githubusercontent.com/openshift/insights-operator/release-4.12/docs/gather-job.yaml[] +include::https://raw.githubusercontent.com/openshift/insights-operator/release-4.13/docs/gather-job.yaml[] ---- . Copy your `insights-operator` image version: + diff --git a/modules/installation-aws-upload-custom-rhcos-ami.adoc b/modules/installation-aws-upload-custom-rhcos-ami.adoc index 40b6e9e60b..ad968b29db 100644 --- a/modules/installation-aws-upload-custom-rhcos-ami.adoc +++ b/modules/installation-aws-upload-custom-rhcos-ami.adoc @@ -58,7 +58,7 @@ variable: ---- $ export RHCOS_VERSION= <1> ---- -<1> The {op-system} VMDK version, like `4.12.0`. +<1> The {op-system} VMDK version, like `4.13.0`. . Export the Amazon S3 bucket name as an environment variable: + diff --git a/modules/installation-complete-user-infra.adoc b/modules/installation-complete-user-infra.adoc index b3ac42e733..e8edc79145 100644 --- a/modules/installation-complete-user-infra.adoc +++ b/modules/installation-complete-user-infra.adoc @@ -68,37 +68,37 @@ $ watch -n5 oc get clusteroperators [source,terminal] ---- NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE -authentication 4.12.0 True False False 19m -baremetal 4.12.0 True False False 37m -cloud-credential 4.12.0 True False False 40m -cluster-autoscaler 4.12.0 True False False 37m -config-operator 4.12.0 True False False 38m -console 4.12.0 True False False 26m -csi-snapshot-controller 4.12.0 True False False 37m -dns 4.12.0 True False False 37m -etcd 4.12.0 True False False 36m -image-registry 4.12.0 True False False 31m -ingress 4.12.0 True False False 30m -insights 4.12.0 True False False 31m -kube-apiserver 4.12.0 True False False 26m -kube-controller-manager 4.12.0 True False False 36m -kube-scheduler 4.12.0 True False False 36m -kube-storage-version-migrator 4.12.0 True False False 37m -machine-api 4.12.0 True False False 29m -machine-approver 4.12.0 True False False 37m -machine-config 4.12.0 True False False 36m -marketplace 4.12.0 True False False 37m -monitoring 4.12.0 True False False 29m -network 4.12.0 True False False 38m -node-tuning 4.12.0 True False False 37m -openshift-apiserver 4.12.0 True False False 32m -openshift-controller-manager 4.12.0 True False False 30m -openshift-samples 4.12.0 True False False 32m -operator-lifecycle-manager 4.12.0 True False False 37m -operator-lifecycle-manager-catalog 4.12.0 True False False 37m -operator-lifecycle-manager-packageserver 4.12.0 True False False 32m -service-ca 4.12.0 True False False 38m -storage 4.12.0 True False False 37m +authentication 4.13.0 True False False 19m +baremetal 4.13.0 True False False 37m +cloud-credential 4.13.0 True False False 40m +cluster-autoscaler 4.13.0 True False False 37m +config-operator 4.13.0 True False False 38m +console 4.13.0 True False False 26m +csi-snapshot-controller 4.13.0 True False False 37m +dns 4.13.0 True False False 37m +etcd 4.13.0 True False False 36m +image-registry 4.13.0 True False False 31m +ingress 4.13.0 True False False 30m +insights 4.13.0 True False False 31m +kube-apiserver 4.13.0 True False False 26m +kube-controller-manager 4.13.0 True False False 36m +kube-scheduler 4.13.0 True False False 36m +kube-storage-version-migrator 4.13.0 True False False 37m +machine-api 4.13.0 True False False 29m +machine-approver 4.13.0 True False False 37m +machine-config 4.13.0 True False False 36m +marketplace 4.13.0 True False False 37m +monitoring 4.13.0 True False False 29m +network 4.13.0 True False False 38m +node-tuning 4.13.0 True False False 37m +openshift-apiserver 4.13.0 True False False 32m +openshift-controller-manager 4.13.0 True False False 30m +openshift-samples 4.13.0 True False False 32m +operator-lifecycle-manager 4.13.0 True False False 37m +operator-lifecycle-manager-catalog 4.13.0 True False False 37m +operator-lifecycle-manager-packageserver 4.13.0 True False False 32m +service-ca 4.13.0 True False False 38m +storage 4.13.0 True False False 37m ---- + Alternatively, the following command notifies you when all of the clusters are available. It also retrieves and displays credentials: diff --git a/modules/installation-disk-partitioning-upi-templates.adoc b/modules/installation-disk-partitioning-upi-templates.adoc index 8f85072365..2a8d332ceb 100644 --- a/modules/installation-disk-partitioning-upi-templates.adoc +++ b/modules/installation-disk-partitioning-upi-templates.adoc @@ -86,7 +86,7 @@ $ ls $HOME/clusterconfig/openshift/ [source,yaml] ---- variant: openshift -version: 4.12.0 +version: 4.13.0 metadata: labels: machineconfiguration.openshift.io/role: worker diff --git a/modules/installation-disk-partitioning.adoc b/modules/installation-disk-partitioning.adoc index 7211bf184f..9b595ba6f8 100644 --- a/modules/installation-disk-partitioning.adoc +++ b/modules/installation-disk-partitioning.adoc @@ -88,7 +88,7 @@ $ ls $HOME/clusterconfig/openshift/ [source,yaml] ---- variant: openshift -version: 4.12.0 +version: 4.13.0 metadata: labels: machineconfiguration.openshift.io/role: worker diff --git a/modules/installation-operators-config.adoc b/modules/installation-operators-config.adoc index 2eff156963..307ee72ac2 100644 --- a/modules/installation-operators-config.adoc +++ b/modules/installation-operators-config.adoc @@ -37,36 +37,36 @@ $ watch -n5 oc get clusteroperators [source,terminal] ---- NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE -authentication 4.12.0 True False False 19m -baremetal 4.12.0 True False False 37m -cloud-credential 4.12.0 True False False 40m -cluster-autoscaler 4.12.0 True False False 37m -config-operator 4.12.0 True False False 38m -console 4.12.0 True False False 26m -csi-snapshot-controller 4.12.0 True False False 37m -dns 4.12.0 True False False 37m -etcd 4.12.0 True False False 36m -image-registry 4.12.0 True False False 31m -ingress 4.12.0 True False False 30m -insights 4.12.0 True False False 31m -kube-apiserver 4.12.0 True False False 26m -kube-controller-manager 4.12.0 True False False 36m -kube-scheduler 4.12.0 True False False 36m -kube-storage-version-migrator 4.12.0 True False False 37m -machine-api 4.12.0 True False False 29m -machine-approver 4.12.0 True False False 37m -machine-config 4.12.0 True False False 36m -marketplace 4.12.0 True False False 37m -monitoring 4.12.0 True False False 29m -network 4.12.0 True False False 38m -node-tuning 4.12.0 True False False 37m -openshift-apiserver 4.12.0 True False False 32m -openshift-controller-manager 4.12.0 True False False 30m -openshift-samples 4.12.0 True False False 32m -operator-lifecycle-manager 4.12.0 True False False 37m -operator-lifecycle-manager-catalog 4.12.0 True False False 37m -operator-lifecycle-manager-packageserver 4.12.0 True False False 32m -service-ca 4.12.0 True False False 38m -storage 4.12.0 True False False 37m +authentication 4.13.0 True False False 19m +baremetal 4.13.0 True False False 37m +cloud-credential 4.13.0 True False False 40m +cluster-autoscaler 4.13.0 True False False 37m +config-operator 4.13.0 True False False 38m +console 4.13.0 True False False 26m +csi-snapshot-controller 4.13.0 True False False 37m +dns 4.13.0 True False False 37m +etcd 4.13.0 True False False 36m +image-registry 4.13.0 True False False 31m +ingress 4.13.0 True False False 30m +insights 4.13.0 True False False 31m +kube-apiserver 4.13.0 True False False 26m +kube-controller-manager 4.13.0 True False False 36m +kube-scheduler 4.13.0 True False False 36m +kube-storage-version-migrator 4.13.0 True False False 37m +machine-api 4.13.0 True False False 29m +machine-approver 4.13.0 True False False 37m +machine-config 4.13.0 True False False 36m +marketplace 4.13.0 True False False 37m +monitoring 4.13.0 True False False 29m +network 4.13.0 True False False 38m +node-tuning 4.13.0 True False False 37m +openshift-apiserver 4.13.0 True False False 32m +openshift-controller-manager 4.13.0 True False False 30m +openshift-samples 4.13.0 True False False 32m +operator-lifecycle-manager 4.13.0 True False False 37m +operator-lifecycle-manager-catalog 4.13.0 True False False 37m +operator-lifecycle-manager-packageserver 4.13.0 True False False 32m +service-ca 4.13.0 True False False 38m +storage 4.13.0 True False False 37m ---- . Configure the Operators that are not available. diff --git a/modules/installation-requirements-user-infra-ibm-z-kvm.adoc b/modules/installation-requirements-user-infra-ibm-z-kvm.adoc index b076397fc5..012f1eaf3f 100644 --- a/modules/installation-requirements-user-infra-ibm-z-kvm.adoc +++ b/modules/installation-requirements-user-infra-ibm-z-kvm.adoc @@ -70,7 +70,7 @@ You can install {product-title} version {product-version} on the following IBM h [NOTE] ==== -Support for {op-system} functionality for IBM z13 all models, {linuxoneProductName} Emperor, and {linuxoneProductName} Rockhopper is deprecated. These hardware models remain fully supported in {product-title} 4.12. However, Red Hat recommends that you use later hardware models. +Support for {op-system} functionality for IBM z13 all models, {linuxoneProductName} Emperor, and {linuxoneProductName} Rockhopper is deprecated. These hardware models remain fully supported in {product-title} 4.13. However, Red Hat recommends that you use later hardware models. ==== [id="minimum-ibm-z-system-requirements_{context}"] diff --git a/modules/installation-special-config-butane-create.adoc b/modules/installation-special-config-butane-create.adoc index d3832889e9..c282326e5e 100644 --- a/modules/installation-special-config-butane-create.adoc +++ b/modules/installation-special-config-butane-create.adoc @@ -19,7 +19,7 @@ You can use Butane to produce a `MachineConfig` object so that you can configure [source,yaml] ---- variant: openshift -version: 4.12.0 +version: 4.13.0 metadata: name: 99-worker-custom labels: diff --git a/modules/installation-special-config-chrony.adoc b/modules/installation-special-config-chrony.adoc index fbe63f5f86..058b36b02b 100644 --- a/modules/installation-special-config-chrony.adoc +++ b/modules/installation-special-config-chrony.adoc @@ -38,7 +38,7 @@ See "Creating machine configs with Butane" for information about Butane. [source,yaml] ---- variant: openshift -version: 4.12.0 +version: 4.13.0 metadata: name: 99-worker-chrony <1> labels: diff --git a/modules/installation-special-config-kmod.adoc b/modules/installation-special-config-kmod.adoc index ac64925bce..375c7dcb4c 100644 --- a/modules/installation-special-config-kmod.adoc +++ b/modules/installation-special-config-kmod.adoc @@ -388,7 +388,7 @@ See "Creating machine configs with Butane" for information about Butane. [source,yaml] ---- variant: openshift -version: 4.12.0 +version: 4.13.0 metadata: name: 99-simple-kmod labels: diff --git a/modules/installation-special-config-raid.adoc b/modules/installation-special-config-raid.adoc index bdceaa5ce3..6d14dbab84 100644 --- a/modules/installation-special-config-raid.adoc +++ b/modules/installation-special-config-raid.adoc @@ -27,7 +27,7 @@ Butane is a command-line utility that {product-title} uses to provide convenient [source,yaml] ---- variant: openshift -version: 4.12.0 +version: 4.13.0 metadata: name: raid1-storage labels: @@ -70,7 +70,7 @@ storage: [source,yaml] ---- variant: openshift -version: 4.12.0 +version: 4.13.0 metadata: name: raid1-alt-storage labels: diff --git a/modules/installation-special-config-storage.adoc b/modules/installation-special-config-storage.adoc index 07916d2972..a42e636cbc 100644 --- a/modules/installation-special-config-storage.adoc +++ b/modules/installation-special-config-storage.adoc @@ -62,7 +62,7 @@ For example, the `threshold` value of `2` in the following configuration can be [source,yaml] ---- variant: openshift -version: 4.12.0 +version: 4.13.0 metadata: name: worker-storage labels: @@ -209,7 +209,7 @@ For example, to configure storage for compute nodes, create a `$HOME/clusterconf .Butane config example for a boot device ---- variant: openshift -version: 4.12.0 +version: 4.13.0 metadata: name: worker-storage <1> labels: diff --git a/modules/installation-user-infra-machines-advanced.adoc b/modules/installation-user-infra-machines-advanced.adoc index c970f8c731..e621859062 100644 --- a/modules/installation-user-infra-machines-advanced.adoc +++ b/modules/installation-user-infra-machines-advanced.adoc @@ -132,7 +132,7 @@ $ openshift-install create manifests --dir [source,yaml] ---- variant: openshift -version: 4.12.0 +version: 4.13.0 metadata: labels: machineconfiguration.openshift.io/role: worker diff --git a/modules/ipi-install-configuring-ntp-for-disconnected-clusters.adoc b/modules/ipi-install-configuring-ntp-for-disconnected-clusters.adoc index 87d50c52cb..55fafdc0a3 100644 --- a/modules/ipi-install-configuring-ntp-for-disconnected-clusters.adoc +++ b/modules/ipi-install-configuring-ntp-for-disconnected-clusters.adoc @@ -35,7 +35,7 @@ See "Creating machine configs with Butane" for information about Butane. .Butane config example ---- variant: openshift -version: 4.12.0 +version: 4.13.0 metadata: name: 99-master-chrony-conf-override labels: @@ -93,7 +93,7 @@ $ butane 99-master-chrony-conf-override.bu -o 99-master-chrony-conf-override.yam .Butane config example ---- variant: openshift -version: 4.12.0 +version: 4.13.0 metadata: name: 99-worker-chrony-conf-override labels: diff --git a/modules/ipi-install-troubleshooting-ntp-out-of-sync.adoc b/modules/ipi-install-troubleshooting-ntp-out-of-sync.adoc index 9e0b81cbd8..f6c2fab414 100644 --- a/modules/ipi-install-troubleshooting-ntp-out-of-sync.adoc +++ b/modules/ipi-install-troubleshooting-ntp-out-of-sync.adoc @@ -66,7 +66,7 @@ See "Creating machine configs with Butane" for information about Butane. [source,yaml] ---- variant: openshift -version: 4.12.0 +version: 4.13.0 metadata: name: 99-master-chrony labels: diff --git a/modules/k8s-nmstate-deploying-nmstate-CLI.adoc b/modules/k8s-nmstate-deploying-nmstate-CLI.adoc index a6001b3d6b..0d7607f198 100644 --- a/modules/k8s-nmstate-deploying-nmstate-CLI.adoc +++ b/modules/k8s-nmstate-deploying-nmstate-CLI.adoc @@ -99,5 +99,5 @@ oc get clusterserviceversion -n openshift-nmstate \ [source, terminal] ---- Name Phase -kubernetes-nmstate-operator.4.12.0-202210210157 Succeeded +kubernetes-nmstate-operator.4.13.0-202210210157 Succeeded ---- diff --git a/modules/machineconfig-modify-journald.adoc b/modules/machineconfig-modify-journald.adoc index 29d892ce54..4c06125763 100644 --- a/modules/machineconfig-modify-journald.adoc +++ b/modules/machineconfig-modify-journald.adoc @@ -27,7 +27,7 @@ See "Creating machine configs with Butane" for information about Butane. [source,yaml] ---- variant: openshift -version: 4.12.0 +version: 4.13.0 metadata: name: 40-worker-custom-journald labels: diff --git a/modules/manually-maintained-credentials-upgrade.adoc b/modules/manually-maintained-credentials-upgrade.adoc index 167e741f0b..70054c7be2 100644 --- a/modules/manually-maintained-credentials-upgrade.adoc +++ b/modules/manually-maintained-credentials-upgrade.adoc @@ -17,9 +17,9 @@ endif::[] The Cloud Credential Operator (CCO) `Upgradable` status for a cluster with manually maintained credentials is `False` by default. -* For minor releases, for example, from 4.11 to 4.12, this status prevents you from upgrading until you have addressed any updated permissions and annotated the `CloudCredential` resource to indicate that the permissions are updated as needed for the next version. This annotation changes the `Upgradable` status to `True`. +* For minor releases, for example, from 4.12 to 4.13, this status prevents you from upgrading until you have addressed any updated permissions and annotated the `CloudCredential` resource to indicate that the permissions are updated as needed for the next version. This annotation changes the `Upgradable` status to `True`. -* For z-stream releases, for example, from 4.12.0 to 4.12.1, no permissions are added or changed, so the upgrade is not blocked. +* For z-stream releases, for example, from 4.13.0 to 4.13.1, no permissions are added or changed, so the upgrade is not blocked. Before upgrading a cluster with manually maintained credentials, you must create any new credentials for the release image that you are upgrading to. Additionally, you must review the required permissions for existing credentials and accommodate any new permissions requirements in the new release for those components. diff --git a/modules/nodes-cluster-resource-override-deploy-cli.adoc b/modules/nodes-cluster-resource-override-deploy-cli.adoc index 45b7452339..787cb387ca 100644 --- a/modules/nodes-cluster-resource-override-deploy-cli.adoc +++ b/modules/nodes-cluster-resource-override-deploy-cli.adoc @@ -85,7 +85,7 @@ metadata: name: clusterresourceoverride namespace: clusterresourceoverride-operator spec: - channel: "4.12" + channel: "4.13" name: clusterresourceoverride source: redhat-operators sourceNamespace: openshift-marketplace diff --git a/modules/nvidia-gpu-gcp-adding-a-gpu-node.adoc b/modules/nvidia-gpu-gcp-adding-a-gpu-node.adoc index 596cfaa274..74672e4d0b 100644 --- a/modules/nvidia-gpu-gcp-adding-a-gpu-node.adoc +++ b/modules/nvidia-gpu-gcp-adding-a-gpu-node.adoc @@ -213,14 +213,14 @@ $ oc get machineset myclustername-2pt9p-worker-a -n openshift-machine-api -o jso + [source,terminal] ---- -jq .spec.template.spec.providerSpec.value.machineType ocp_4.12_machineset-a2-highgpu-1g.json +jq .spec.template.spec.providerSpec.value.machineType ocp_4.13_machineset-a2-highgpu-1g.json "a2-highgpu-1g" ---- + -The `` file is saved as `ocp_4.12_machineset-a2-highgpu-1g.json`. +The `` file is saved as `ocp_4.13_machineset-a2-highgpu-1g.json`. -. Update the following fields in `ocp_4.12_machineset-a2-highgpu-1g.json`: +. Update the following fields in `ocp_4.13_machineset-a2-highgpu-1g.json`: + * Change `.metadata.name` to a name containing `gpu`. @@ -244,7 +244,7 @@ to match the new `.metadata.name`. + [source,terminal] ---- -$ oc get machineset/myclustername-2pt9p-worker-a -n openshift-machine-api -o json | diff ocp_4.12_machineset-a2-highgpu-1g.json - +$ oc get machineset/myclustername-2pt9p-worker-a -n openshift-machine-api -o json | diff ocp_4.13_machineset-a2-highgpu-1g.json - ---- + .Example output @@ -274,7 +274,7 @@ $ oc get machineset/myclustername-2pt9p-worker-a -n openshift-machine-api -o jso + [source,terminal] ---- -$ oc create -f ocp_4.12_machineset-a2-highgpu-1g.json +$ oc create -f ocp_4.13_machineset-a2-highgpu-1g.json ---- + .Example output diff --git a/modules/nw-configuring-lb-allowed-source-ranges-migration.adoc b/modules/nw-configuring-lb-allowed-source-ranges-migration.adoc index d521ae4e48..e21d8121bc 100644 --- a/modules/nw-configuring-lb-allowed-source-ranges-migration.adoc +++ b/modules/nw-configuring-lb-allowed-source-ranges-migration.adoc @@ -53,7 +53,7 @@ spec: ... ---- -. Update your cluster to {product-title} 4.12. +. Update your cluster to {product-title} 4.13. . Set the allowed source ranges API for the `ingresscontroller` by running the following command: + diff --git a/modules/nw-infw-operator-installing.adoc b/modules/nw-infw-operator-installing.adoc index fde3f54fb8..570437bda3 100644 --- a/modules/nw-infw-operator-installing.adoc +++ b/modules/nw-infw-operator-installing.adoc @@ -79,7 +79,7 @@ $ oc get ip -n openshift-ingress-node-firewall [source,terminal] ---- NAME CSV APPROVAL APPROVED -install-5cvnz ingress-node-firewall.4.12.0-202211122336 Automatic true +install-5cvnz ingress-node-firewall.4.13.0-202211122336 Automatic true ---- . To verify the version of the Operator, enter the following command: @@ -94,7 +94,7 @@ $ oc get csv -n openshift-ingress-node-firewall [source,terminal] ---- NAME DISPLAY VERSION REPLACES PHASE -ingress-node-firewall.4.12.0-202211122336 Ingress Node Firewall Operator 4.12.0-202211122336 ingress-node-firewall.4.12.0-202211102047 Succeeded +ingress-node-firewall.4.13.0-202211122336 Ingress Node Firewall Operator 4.13.0-202211122336 ingress-node-firewall.4.13.0-202211102047 Succeeded ---- [id="install-operator-web-console_{context}"] diff --git a/modules/nw-metalLB-basic-upgrade-operator.adoc b/modules/nw-metalLB-basic-upgrade-operator.adoc index a5a9039cfd..7f2dd54588 100644 --- a/modules/nw-metalLB-basic-upgrade-operator.adoc +++ b/modules/nw-metalLB-basic-upgrade-operator.adoc @@ -61,4 +61,3 @@ $ oc get csv -n metallb-system NAME DISPLAY VERSION REPLACES PHASE metallb-operator.4.{product-version}.0-202207051316 MetalLB Operator 4.{product-version}.0-202207051316 Succeeded ---- - diff --git a/modules/nw-metalLB-monitor-upgrading.adoc b/modules/nw-metalLB-monitor-upgrading.adoc index 53201cfb5a..7ae9ad826d 100644 --- a/modules/nw-metalLB-monitor-upgrading.adoc +++ b/modules/nw-metalLB-monitor-upgrading.adoc @@ -34,8 +34,8 @@ $ oc get csv [source,terminal] ---- VERSION REPLACES PHASE -4.12.0 metallb-operator.4.12-nnnnnnnnnnnn Installing -4.12.0 Replacing +4.13.0 metallb-operator.4.13-nnnnnnnnnnnn Installing +4.13.0 Replacing ---- . Run `get csv` again to verify the output: @@ -49,5 +49,5 @@ $ oc get csv [source,terminal] ---- NAME DISPLAY VERSION REPLACES PHASE -metallb-operator.4.12-nnnnnnnnnnnn MetalLB 4.12.0 metallb-operator.v4.12.0 Succeeded +metallb-operator.4.13-nnnnnnnnnnnn MetalLB 4.13.0 metallb-operator.v4.13.0 Succeeded ---- diff --git a/modules/nw-openstack-external-ccm.adoc b/modules/nw-openstack-external-ccm.adoc index 4ed0cc3251..0e2bee7135 100644 --- a/modules/nw-openstack-external-ccm.adoc +++ b/modules/nw-openstack-external-ccm.adoc @@ -7,7 +7,7 @@ [id="nw-openstack-external-ccm_{context}"] = The OpenStack Cloud Controller Manager -In {product-title} 4.12, clusters that run on {rh-openstack-first} are switched from the legacy OpenStack cloud provider to the external OpenStack Cloud Controller Manager (CCM). This change follows the move in Kubernetes from in-tree, legacy cloud providers to external cloud providers that are implemented by using the link:https://kubernetes.io/docs/concepts/architecture/cloud-controller/[Cloud Controller Manager]. +Beginning with {product-title} 4.12, clusters that run on {rh-openstack-first} were switched from the legacy OpenStack cloud provider to the external OpenStack Cloud Controller Manager (CCM). This change follows the move in Kubernetes from in-tree, legacy cloud providers to external cloud providers that are implemented by using the link:https://kubernetes.io/docs/concepts/architecture/cloud-controller/[Cloud Controller Manager]. To preserve user-defined configurations for the legacy cloud provider, existing configurations are mapped to new ones as part of the migration process. It searches for a configuration called `cloud-provider-config` in the `openshift-config` namespace. diff --git a/modules/nw-ptp-installing-operator-cli.adoc b/modules/nw-ptp-installing-operator-cli.adoc index 6f70095bc6..b3acec1066 100644 --- a/modules/nw-ptp-installing-operator-cli.adoc +++ b/modules/nw-ptp-installing-operator-cli.adoc @@ -99,5 +99,5 @@ $ oc get csv -n openshift-ptp -o custom-columns=Name:.metadata.name,Phase:.statu [source,terminal] ---- Name Phase -4.12.0-202301261535 Succeeded +4.13.0-202301261535 Succeeded ---- diff --git a/modules/nw-rosa-proxy-remove-cli.adoc b/modules/nw-rosa-proxy-remove-cli.adoc index a1e7445503..0c79109ab4 100644 --- a/modules/nw-rosa-proxy-remove-cli.adoc +++ b/modules/nw-rosa-proxy-remove-cli.adoc @@ -50,7 +50,7 @@ Before removal, the proxy IP displays in a proxy section: Name: ID: External ID: -OpenShift Version: 4.12.0 +OpenShift Version: 4.13.0 Channel Group: stable DNS: AWS Account: @@ -80,7 +80,7 @@ After removing the proxy, the proxy section is removed: Name: ID: External ID: -OpenShift Version: 4.12.0 +OpenShift Version: 4.13.0 Channel Group: stable DNS: AWS Account: diff --git a/modules/nw-sriov-installing-operator.adoc b/modules/nw-sriov-installing-operator.adoc index 667e74e67d..aea6af35b4 100644 --- a/modules/nw-sriov-installing-operator.adoc +++ b/modules/nw-sriov-installing-operator.adoc @@ -92,7 +92,7 @@ $ oc get csv -n openshift-sriov-network-operator \ [source,terminal] ---- Name Phase -sriov-network-operator.4.12.0-202310121402 Succeeded +sriov-network-operator.4.13.0-202310121402 Succeeded ---- [id="install-operator-web-console_{context}"] diff --git a/modules/oadp-installing-oadp-rosa-sts.adoc b/modules/oadp-installing-oadp-rosa-sts.adoc index 421a91d68e..fab13ae93e 100644 --- a/modules/oadp-installing-oadp-rosa-sts.adoc +++ b/modules/oadp-installing-oadp-rosa-sts.adoc @@ -16,7 +16,7 @@ Restic is not supported in the OADP on ROSA with AWS STS environment. Ensure the .Prerequisites * A ROSA OpenShift Cluster with the required access and tokens. -* link:https://docs.openshift.com/container-platform/4.12/backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.html#oadp-creating-default-secret_installing-oadp-aws[A default Secret], if your backup and snapshot locations use the same credentials, or if you do not require a snapshot location. +* link:https://docs.openshift.com/container-platform/4.13/backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.html#oadp-creating-default-secret_installing-oadp-aws[A default Secret], if your backup and snapshot locations use the same credentials, or if you do not require a snapshot location. .Procedure @@ -122,6 +122,6 @@ You are now ready to backup and restore OpenShift applications, as described in * link:https://docs.openshift.com/rosa/rosa_architecture/rosa-understanding.html[Understanding ROSA with STS] * link:https://docs.openshift.com/rosa/rosa_getting_started/rosa-sts-getting-started-workflow.html[Getting started with ROSA STS] * link:https://docs.openshift.com/rosa/rosa_install_access_delete_clusters/rosa-sts-creating-a-cluster-quickly.html[Creating a ROSA cluster with STS] -* link:https://docs.openshift.com/container-platform/4.12/backup_and_restore/application_backup_and_restore/installing/about-installing-oadp.html[About installing OADP] -* link:https://docs.openshift.com/container-platform/4.12/storage/container_storage_interface/persistent-storage-csi.html[Configuring CSI volumes] +* link:https://docs.openshift.com/container-platform/4.13/backup_and_restore/application_backup_and_restore/installing/about-installing-oadp.html[About installing OADP] +* link:https://docs.openshift.com/container-platform/4.13/storage/container_storage_interface/persistent-storage-csi.html[Configuring CSI volumes] * link:https://docs.openshift.com/rosa/rosa_architecture/rosa_policy_service_definition/rosa-service-definition.html#rosa-sdpolicy-storage_rosa-service-definition[ROSA storage options] diff --git a/modules/oauth-configuring-token-inactivity-timeout.adoc b/modules/oauth-configuring-token-inactivity-timeout.adoc index 40b3d6f033..6c693ce59b 100644 --- a/modules/oauth-configuring-token-inactivity-timeout.adoc +++ b/modules/oauth-configuring-token-inactivity-timeout.adoc @@ -58,7 +58,7 @@ Do not continue to the next step until `PROGRESSING` is listed as `False`, as sh [source,terminal] ---- NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE -authentication 4.12.0 True False False 145m +authentication 4.13.0 True False False 145m ---- . Check that a new revision of the Kubernetes API server pods has rolled out. This will take several minutes. @@ -74,7 +74,7 @@ Do not continue to the next step until `PROGRESSING` is listed as `False`, as sh [source,terminal] ---- NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE -kube-apiserver 4.12.0 True False False 145m +kube-apiserver 4.13.0 True False False 145m ---- + If `PROGRESSING` is showing `True`, wait a few minutes and try again. diff --git a/modules/oc-mirror-creating-image-set-config.adoc b/modules/oc-mirror-creating-image-set-config.adoc index aef73996a2..480543e5f5 100644 --- a/modules/oc-mirror-creating-image-set-config.adoc +++ b/modules/oc-mirror-creating-image-set-config.adoc @@ -44,11 +44,11 @@ storageConfig: <2> mirror: platform: channels: - - name: stable-4.12 <4> + - name: stable-4.13 <4> type: ocp graph: true <5> operators: - - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.12 <6> + - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.13 <6> packages: - name: serverless-operator <7> channels: diff --git a/modules/oc-mirror-image-set-config-examples.adoc b/modules/oc-mirror-image-set-config-examples.adoc index be63e96ce7..9c94c3cd5d 100644 --- a/modules/oc-mirror-image-set-config-examples.adoc +++ b/modules/oc-mirror-image-set-config-examples.adoc @@ -30,9 +30,9 @@ mirror: architectures: - "s390x" channels: - - name: stable-4.12 + - name: stable-4.13 operators: - - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.12 + - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.13 helm: repositories: - name: redhat-helm-charts @@ -60,7 +60,7 @@ storageConfig: path: /home/user/metadata mirror: operators: - - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.12 + - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.13 packages: - name: rhacs-operator channels: diff --git a/modules/oc-mirror-imageset-config-params.adoc b/modules/oc-mirror-imageset-config-params.adoc index e619e72459..a3059dd6ac 100644 --- a/modules/oc-mirror-imageset-config-params.adoc +++ b/modules/oc-mirror-imageset-config-params.adoc @@ -112,7 +112,7 @@ repositories: [source,yaml] ---- operators: - - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.12 + - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.13 packages: - name: elasticsearch-operator minVersion: '2.4.0' @@ -120,7 +120,7 @@ operators: |`mirror.operators.catalog` |The Operator catalog to include in the image set. -|String. For example: `registry.redhat.io/redhat/redhat-operator-index:v4.12`. +|String. For example: `registry.redhat.io/redhat/redhat-operator-index:v4.13`. |`mirror.operators.full` |When `true`, downloads the full catalog, Operator package, or Operator channel. @@ -133,7 +133,7 @@ operators: [source,yaml] ---- operators: - - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.12 + - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.13 packages: - name: elasticsearch-operator minVersion: '5.2.3-31' @@ -149,7 +149,7 @@ operators: |`mirror.operators.packages.channels.name` |The Operator channel name, unique within a package, to include in the image set. -|String. For example: `fast` or `stable-v4.12`. +|String. For example: `fast` or `stable-v4.13`. |`mirror.operators.packages.channels.maxVersion` |The highest version of the Operator mirror across all channels in which it exists. @@ -206,7 +206,7 @@ architectures: ---- channels: - name: stable-4.10 - - name: stable-4.12 + - name: stable-4.13 ---- |`mirror.platform.channels.full` @@ -215,7 +215,7 @@ channels: |`mirror.platform.channels.name` |The name of the release channel. -|String. For example: `stable-4.12` +|String. For example: `stable-4.13` |`mirror.platform.channels.minVersion` |The minimum version of the referenced platform to be mirrored. @@ -223,7 +223,7 @@ channels: |`mirror.platform.channels.maxVersion` |The highest version of the referenced platform to be mirrored. -|String. For example: `4.12.1` +|String. For example: `4.13.1` |`mirror.platform.channels.shortestPath` |Toggles shortest path mirroring or full range mirroring. diff --git a/modules/oc-mirror-oci-format.adoc b/modules/oc-mirror-oci-format.adoc index 8ed7b643d5..c4a6702f88 100644 --- a/modules/oc-mirror-oci-format.adoc +++ b/modules/oc-mirror-oci-format.adoc @@ -31,7 +31,7 @@ kind: ImageSetConfiguration apiVersion: mirror.openshift.io/v1alpha2 mirror: operators: - - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.12 + - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.13 packages: - name: aws-load-balancer-operator ---- diff --git a/modules/odc-accessing-perspectives.adoc b/modules/odc-accessing-perspectives.adoc index 4a548331fe..3b5b05b1e1 100644 --- a/modules/odc-accessing-perspectives.adoc +++ b/modules/odc-accessing-perspectives.adoc @@ -13,7 +13,7 @@ You can access the *Administrator* and *Developer* perspective from the web cons To access a perspective, ensure that you have logged in to the web console. Your default perspective is automatically determined by the permission of the users. The *Administrator* perspective is selected for users with access to all projects, while the *Developer* perspective is selected for users with limited access to their own projects .Additional Resources -See link:https://docs.openshift.com/container-platform/4.12/web_console/adding-user-preferences.html[Adding User Preferences] for more information on changing perspectives. +See link:https://docs.openshift.com/container-platform/4.13/web_console/adding-user-preferences.html[Adding User Preferences] for more information on changing perspectives. .Procedure diff --git a/modules/olm-catalogsource-image-template.adoc b/modules/olm-catalogsource-image-template.adoc index 2f86765c46..cb1fa20259 100644 --- a/modules/olm-catalogsource-image-template.adoc +++ b/modules/olm-catalogsource-image-template.adoc @@ -12,20 +12,20 @@ endif::[] [id="olm-catalogsource-image-template_{context}"] = Image template for custom catalog sources -Operator compatibility with the underlying cluster can be expressed by a catalog source in various ways. One way, which is used for the default Red Hat-provided catalog sources, is to identify image tags for index images that are specifically created for a particular platform release, for example {product-title} 4.12. +Operator compatibility with the underlying cluster can be expressed by a catalog source in various ways. One way, which is used for the default Red Hat-provided catalog sources, is to identify image tags for index images that are specifically created for a particular platform release, for example {product-title} 4.13. -During a cluster upgrade, the index image tag for the default Red Hat-provided catalog sources are updated automatically by the Cluster Version Operator (CVO) so that Operator Lifecycle Manager (OLM) pulls the updated version of the catalog. For example during an upgrade from {product-title} 4.11 to 4.12, the `spec.image` field in the `CatalogSource` object for the `redhat-operators` catalog is updated from: +During a cluster upgrade, the index image tag for the default Red Hat-provided catalog sources are updated automatically by the Cluster Version Operator (CVO) so that Operator Lifecycle Manager (OLM) pulls the updated version of the catalog. For example during an upgrade from {product-title} 4.12 to 4.13, the `spec.image` field in the `CatalogSource` object for the `redhat-operators` catalog is updated from: [source,terminal] ---- -registry.redhat.io/redhat/redhat-operator-index:v4.11 +registry.redhat.io/redhat/redhat-operator-index:v4.12 ---- to: [source,terminal] ---- -registry.redhat.io/redhat/redhat-operator-index:v4.12 +registry.redhat.io/redhat/redhat-operator-index:v4.13 ---- However, the CVO does not automatically update image tags for custom catalogs. To ensure users are left with a compatible and supported Operator installation after a cluster upgrade, custom catalogs should also be kept updated to reference an updated index image. @@ -77,7 +77,7 @@ If the `spec.image` field and the `olm.catalogImageTemplate` annotation are both If the `spec.image` field is not set and the annotation does not resolve to a usable pull spec, OLM stops reconciliation of the catalog source and sets it into a human-readable error condition. ==== -For an {product-title} 4.12 cluster, which uses Kubernetes 1.25, the `olm.catalogImageTemplate` annotation in the preceding example resolves to the following image reference: +For an {product-title} 4.13 cluster, which uses Kubernetes 1.26, the `olm.catalogImageTemplate` annotation in the preceding example resolves to the following image reference: [source,terminal] ---- diff --git a/modules/olm-deleting-po.adoc b/modules/olm-deleting-po.adoc index 34873ad34c..fb907be7c3 100644 --- a/modules/olm-deleting-po.adoc +++ b/modules/olm-deleting-po.adoc @@ -61,5 +61,5 @@ $ oc get co platform-operators-aggregated [source,terminal] ---- NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE -platform-operators-aggregated 4.12.0-0 True False False 70s +platform-operators-aggregated 4.13.0-0 True False False 70s ---- \ No newline at end of file diff --git a/modules/openshift-cluster-maximums-major-releases.adoc b/modules/openshift-cluster-maximums-major-releases.adoc index f4e5c742be..de39f663bc 100644 --- a/modules/openshift-cluster-maximums-major-releases.adoc +++ b/modules/openshift-cluster-maximums-major-releases.adoc @@ -79,7 +79,7 @@ Red Hat does not provide direct guidance on sizing your {product-title} cluster. [id="cluster-maximums-major-releases-example-scenario_{context}"] == Example scenario -As an example, 500 worker nodes (m5.2xl) were tested, and are supported, using {product-title} 4.12, the OVN-Kubernetes network plugin, and the following workload objects: +As an example, 500 worker nodes (m5.2xl) were tested, and are supported, using {product-title} 4.13, the OVN-Kubernetes network plugin, and the following workload objects: * 200 namespaces, in addition to the defaults * 60 pods per node; 30 server and 30 client pods (30k total) diff --git a/modules/preparing-an-inital-cluster-deployment-for-mce-connected.adoc b/modules/preparing-an-inital-cluster-deployment-for-mce-connected.adoc index 5383428690..f36e727535 100644 --- a/modules/preparing-an-inital-cluster-deployment-for-mce-connected.adoc +++ b/modules/preparing-an-inital-cluster-deployment-for-mce-connected.adoc @@ -238,9 +238,9 @@ $ oc wait localvolume -n openshift-local-storage assisted-service --for conditio apiVersion: hive.openshift.io/v1 kind: ClusterImageSet metadata: - name: "4.12" + name: "4.13" spec: - releaseImage: quay.io/openshift-release-dev/ocp-release:4.12.0-x86_64 + releaseImage: quay.io/openshift-release-dev/ocp-release:4.13.0-x86_64 ---- . Create a manifest to import the agent installed cluster (that hosts the multicluster engine and the Assisted Service) as the hub cluster. diff --git a/modules/preparing-an-inital-cluster-deployment-for-mce-disconnected.adoc b/modules/preparing-an-inital-cluster-deployment-for-mce-disconnected.adoc index 03d6b09864..1ae9c806d7 100644 --- a/modules/preparing-an-inital-cluster-deployment-for-mce-disconnected.adoc +++ b/modules/preparing-an-inital-cluster-deployment-for-mce-disconnected.adoc @@ -36,12 +36,12 @@ To mirror your {product-title} image repository to your mirror registry, you can architectures: - "amd64" channels: - - name: stable-4.12 <4> + - name: stable-4.13 <4> type: ocp additionalImages: - name: registry.redhat.io/ubi8/ubi:latest operators: - - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.12 <5> + - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.13 <5> packages: <6> - name: multicluster-engine <7> - name: local-storage-operator <8> diff --git a/modules/psap-driver-toolkit-pulling.adoc b/modules/psap-driver-toolkit-pulling.adoc index b6492601fc..0d6168f5fc 100644 --- a/modules/psap-driver-toolkit-pulling.adoc +++ b/modules/psap-driver-toolkit-pulling.adoc @@ -44,7 +44,7 @@ $ oc adm release info quay.io/openshift-release-dev/ocp-release:{product-version + .Example output -The output for the `ocp-release:4.12.0-x86_64` image is as follows: +The output for the `ocp-release:4.13.0-x86_64` image is as follows: + [source,terminal] ---- diff --git a/modules/psap-using-node-feature-discovery-operator.adoc b/modules/psap-using-node-feature-discovery-operator.adoc index fb7c40bce2..7bf209c525 100644 --- a/modules/psap-using-node-feature-discovery-operator.adoc +++ b/modules/psap-using-node-feature-discovery-operator.adoc @@ -37,7 +37,7 @@ spec: instance: "" # instance is empty by default topologyupdater: false # False by default operand: - image: registry.redhat.io/openshift4/ose-node-feature-discovery:v4.12 + image: registry.redhat.io/openshift4/ose-node-feature-discovery:v4.13 imagePullPolicy: Always workerConfig: configData: | diff --git a/modules/registry-configuring-storage-baremetal.adoc b/modules/registry-configuring-storage-baremetal.adoc index a1891996e7..88ebc83a20 100644 --- a/modules/registry-configuring-storage-baremetal.adoc +++ b/modules/registry-configuring-storage-baremetal.adoc @@ -116,7 +116,7 @@ $ oc get clusteroperator image-registry [source,terminal] ---- NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE -image-registry 4.12 True False False 6h50m +image-registry 4.13 True False False 6h50m ---- + . Ensure that your registry is set to managed to enable building and pushing of images. diff --git a/modules/restore-replace-stopped-baremetal-etcd-member.adoc b/modules/restore-replace-stopped-baremetal-etcd-member.adoc index 550153e807..41d190e63b 100644 --- a/modules/restore-replace-stopped-baremetal-etcd-member.adoc +++ b/modules/restore-replace-stopped-baremetal-etcd-member.adoc @@ -313,7 +313,7 @@ $ oc get clusteroperator baremetal [source,terminal] ---- NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE -baremetal 4.12.0 True False False 3d15h +baremetal 4.13.0 True False False 3d15h ---- . Remove the old `BareMetalHost` object by running the following command: diff --git a/modules/rhcos-load-firmware-blobs.adoc b/modules/rhcos-load-firmware-blobs.adoc index 1d5000a32d..8e4e7ee656 100644 --- a/modules/rhcos-load-firmware-blobs.adoc +++ b/modules/rhcos-load-firmware-blobs.adoc @@ -21,7 +21,7 @@ See "Creating machine configs with Butane" for information about Butane. [source,yaml] ---- variant: openshift -version: 4.12.0 +version: 4.13.0 metadata: labels: machineconfiguration.openshift.io/role: worker diff --git a/modules/rhel-compute-updating.adoc b/modules/rhel-compute-updating.adoc index 4faf731ed2..d50cc82db7 100644 --- a/modules/rhel-compute-updating.adoc +++ b/modules/rhel-compute-updating.adoc @@ -81,7 +81,7 @@ As of {product-title} 4.11, the Ansible playbooks are provided only for {op-syst [source,terminal] ---- # subscription-manager repos --disable=rhocp-4.11-for-rhel-8-x86_64-rpms \ - --enable=rhocp-4.12-for-rhel-8-x86_64-rpms + --enable=rhocp-4.13-for-rhel-8-x86_64-rpms ---- . Update a {op-system-base} worker machine: diff --git a/modules/rhel-preparing-node.adoc b/modules/rhel-preparing-node.adoc index 303a71b9ae..13c71d57d0 100644 --- a/modules/rhel-preparing-node.adoc +++ b/modules/rhel-preparing-node.adoc @@ -75,7 +75,7 @@ Note that this might take a few minutes if you have a large number of available # subscription-manager repos \ --enable="rhel-8-for-x86_64-baseos-rpms" \ --enable="rhel-8-for-x86_64-appstream-rpms" \ - --enable="rhocp-4.12-for-rhel-8-x86_64-rpms" \ + --enable="rhocp-4.13-for-rhel-8-x86_64-rpms" \ --enable="fast-datapath-for-rhel-8-x86_64-rpms" ---- diff --git a/modules/rhel-preparing-playbook-machine.adoc b/modules/rhel-preparing-playbook-machine.adoc index a9f264a99e..14cff73c8c 100644 --- a/modules/rhel-preparing-playbook-machine.adoc +++ b/modules/rhel-preparing-playbook-machine.adoc @@ -63,7 +63,7 @@ If you use SSH key-based authentication, you must manage the key with an SSH age # subscription-manager repos \ --enable="rhel-8-for-x86_64-baseos-rpms" \ --enable="rhel-8-for-x86_64-appstream-rpms" \ - --enable="rhocp-4.12-for-rhel-8-x86_64-rpms" + --enable="rhocp-4.13-for-rhel-8-x86_64-rpms" ---- . Install the required packages, including `openshift-ansible`: diff --git a/modules/rosa-create-objects.adoc b/modules/rosa-create-objects.adoc index f1c15346e4..79354dab78 100644 --- a/modules/rosa-create-objects.adoc +++ b/modules/rosa-create-objects.adoc @@ -180,7 +180,7 @@ When using `--private-link`, the `--subnet-ids` argument is required and only on |The Amazon Resource Name (ARN) of the role used by Red Hat Site Reliabilty Engineers (SREs) to enable access to the cluster account to provide support. |--version -|The version (string) of {product-title} that will be used to install the cluster or cluster resources, including `account-role`. Example: `4.12` +|The version (string) of {product-title} that will be used to install the cluster or cluster resources, including `account-role`. Example: `4.13` |--worker-iam-role string |The Amazon Resource Name (ARN) of the IAM role that will be attached to compute instances. diff --git a/modules/rosa-hcp-creating-account-wide-sts-roles-and-policies.adoc b/modules/rosa-hcp-creating-account-wide-sts-roles-and-policies.adoc index 6ae60d035d..60dd1d0acc 100644 --- a/modules/rosa-hcp-creating-account-wide-sts-roles-and-policies.adoc +++ b/modules/rosa-hcp-creating-account-wide-sts-roles-and-policies.adoc @@ -36,10 +36,10 @@ $ rosa list account-roles ---- I: Fetching account roles ROLE NAME ROLE TYPE ROLE ARN OPENSHIFT VERSION -ManagedOpenShift-ControlPlane-Role Control plane arn:aws:iam::8744:role/ManagedOpenShift-ControlPlane-Role 4.12 -ManagedOpenShift-Installer-Role Installer arn:aws:iam::8744:role/ManagedOpenShift-Installer-Role 4.12 -ManagedOpenShift-Support-Role Support arn:aws:iam::8744:role/ManagedOpenShift-Support-Role 4.12 -ManagedOpenShift-Worker-Role Worker arn:aws:iam::8744:role/ManagedOpenShift-Worker-Role 4.12 +ManagedOpenShift-ControlPlane-Role Control plane arn:aws:iam::8744:role/ManagedOpenShift-ControlPlane-Role 4.13 +ManagedOpenShift-Installer-Role Installer arn:aws:iam::8744:role/ManagedOpenShift-Installer-Role 4.13 +ManagedOpenShift-Support-Role Support arn:aws:iam::8744:role/ManagedOpenShift-Support-Role 4.13 +ManagedOpenShift-Worker-Role Worker arn:aws:iam::8744:role/ManagedOpenShift-Worker-Role 4.13 ---- . If they do not exist in your AWS account, create the required account-wide STS roles and policies by running the following command: diff --git a/modules/rosa-sts-creating-a-cluster-with-customizations-cli.adoc b/modules/rosa-sts-creating-a-cluster-with-customizations-cli.adoc index e25f833667..f8c9652dc3 100644 --- a/modules/rosa-sts-creating-a-cluster-with-customizations-cli.adoc +++ b/modules/rosa-sts-creating-a-cluster-with-customizations-cli.adoc @@ -68,7 +68,7 @@ I: AWS credentials are valid! I: Validating AWS quota... I: AWS quota ok. If cluster installation fails, validate actual AWS resource usage against https://docs.openshift.com/rosa/rosa_getting_started/rosa-required-aws-service-quotas.html I: Verifying whether OpenShift command-line tool is available... -I: Current OpenShift Client Version: 4.12.0 +I: Current OpenShift Client Version: 4.13.0 I: Creating account roles ? Role prefix: ManagedOpenShift <1> ? Permissions boundary ARN (optional): <2> diff --git a/modules/rosa-sts-creating-a-cluster-with-customizations-ocm.adoc b/modules/rosa-sts-creating-a-cluster-with-customizations-ocm.adoc index 9857a84971..b8cf2701eb 100644 --- a/modules/rosa-sts-creating-a-cluster-with-customizations-ocm.adoc +++ b/modules/rosa-sts-creating-a-cluster-with-customizations-ocm.adoc @@ -158,7 +158,7 @@ I: AWS credentials are valid! I: Validating AWS quota... I: AWS quota ok. If cluster installation fails, validate actual AWS resource usage against https://docs.openshift.com/rosa/rosa_getting_started/rosa-required-aws-service-quotas.html I: Verifying whether OpenShift command-line tool is available... -I: Current OpenShift Client Version: 4.12.0 +I: Current OpenShift Client Version: 4.13.0 I: Creating account roles ? Role prefix: ManagedOpenShift <1> ? Permissions boundary ARN (optional): <2> diff --git a/modules/rosa-sts-interactive-cluster-creation-mode-options.adoc b/modules/rosa-sts-interactive-cluster-creation-mode-options.adoc index 1ca9bab3bc..2d05c22a29 100644 --- a/modules/rosa-sts-interactive-cluster-creation-mode-options.adoc +++ b/modules/rosa-sts-interactive-cluster-creation-mode-options.adoc @@ -23,7 +23,7 @@ The following table describes the interactive cluster creation mode options: |Create an OpenShift cluster that uses the AWS Security Token Service (STS) to allocate temporary, limited-privilege credentials for component-specific AWS Identity and Access Management (IAM) roles. The service enables cluster components to make AWS API calls using secure cloud resource management practices. The default is `Yes`. |`OpenShift version` -|Select the version of OpenShift to install, for example `4.12`. The default is the latest version. +|Select the version of OpenShift to install, for example `4.13`. The default is the latest version. |`Installer role ARN` |If you have more than one set of account roles in your AWS account for your cluster version, a list of installer role ARNs are provided. Select the ARN for the installer role that you want to use with your cluster. The cluster uses the account-wide roles and policies that relate to the selected installer role. diff --git a/modules/sample-ztp-custom-resources.adoc b/modules/sample-ztp-custom-resources.adoc index bf28adf1a7..951f7b6c94 100644 --- a/modules/sample-ztp-custom-resources.adoc +++ b/modules/sample-ztp-custom-resources.adoc @@ -23,7 +23,7 @@ You can customize the following ZTP custom resources to specify more details abo clusterDeploymentRef: name: ostest imageSetRef: - name: openshift-4.12 + name: openshift-4.13 networking: clusterNetwork: - cidr: 10.128.0.0/14 @@ -71,9 +71,9 @@ spec: apiVersion: hive.openshift.io/v1 kind: ClusterImageSet metadata: - name: openshift-4.12 + name: openshift-4.13 spec: - releaseImage: registry.ci.openshift.org/ocp/release:4.12.0-0.nightly-2022-06-06-025509 + releaseImage: registry.ci.openshift.org/ocp/release:4.13.0-0.nightly-2022-06-06-025509 ---- *infra-env.yaml* diff --git a/modules/selecting-cluster-capabilities.adoc b/modules/selecting-cluster-capabilities.adoc index 03454ade8f..3efb5ffe9e 100644 --- a/modules/selecting-cluster-capabilities.adoc +++ b/modules/selecting-cluster-capabilities.adoc @@ -12,11 +12,11 @@ During a customized installation, you create an `install-config.yaml` file that [source,yaml] ---- capabilities: - baselineCapabilitySet: v4.12 <1> + baselineCapabilitySet: v4.13 <1> additionalEnabledCapabilities: <2> - CSISnapshot - Console - Storage ---- -<1> Defines a baseline set of capabilities to install. Valid values are `None`, `v4.11`, `v4.12`, and `vCurrent`. If you select `None`, all optional capabilities will be disabled. The default value is `vCurrent`, which enables all optional capabilities. +<1> Defines a baseline set of capabilities to install. Valid values are `None`, `v4.12`, `v4.13`, and `vCurrent`. If you select `None`, all optional capabilities will be disabled. The default value is `vCurrent`, which enables all optional capabilities. <2> Defines a list of capabilities to explicitly enable. These will be enabled in addition to the capabilities specified in `baselineCapabilitySet`. diff --git a/modules/serverless-quarkus-template.adoc b/modules/serverless-quarkus-template.adoc index 5489d3b49a..aeb693f4d9 100644 --- a/modules/serverless-quarkus-template.adoc +++ b/modules/serverless-quarkus-template.adoc @@ -45,7 +45,7 @@ Both `http` and `event` trigger functions have the same template structure: junit junit - 4.12 + 4.13 test diff --git a/modules/sriov-operator-hosted-control-planes.adoc b/modules/sriov-operator-hosted-control-planes.adoc index 303a0b2d9b..77b71ea0d0 100644 --- a/modules/sriov-operator-hosted-control-planes.adoc +++ b/modules/sriov-operator-hosted-control-planes.adoc @@ -47,7 +47,7 @@ metadata: name: sriov-network-operator-subsription namespace: openshift-sriov-network-operator spec: - channel: "4.12" + channel: "4.13" name: sriov-network-operator config: nodeSelector: @@ -69,7 +69,7 @@ $ oc get csv -n openshift-sriov-network-operator [source,terminal] ---- NAME DISPLAY VERSION REPLACES PHASE -sriov-network-operator.4.12.0-202211021237 SR-IOV Network Operator 4.12.0-202211021237 sriov-network-operator.4.12.0-202210290517 Succeeded +sriov-network-operator.4.13.0-202211021237 SR-IOV Network Operator 4.13.0-202211021237 sriov-network-operator.4.13.0-202210290517 Succeeded ---- . To verify that the SR-IOV pods are deployed, run the following command: diff --git a/modules/troubleshooting-enabling-kdump-day-one.adoc b/modules/troubleshooting-enabling-kdump-day-one.adoc index db9078d575..19175a257e 100644 --- a/modules/troubleshooting-enabling-kdump-day-one.adoc +++ b/modules/troubleshooting-enabling-kdump-day-one.adoc @@ -28,7 +28,7 @@ Create a `MachineConfig` object for cluster-wide configuration: [source,yaml] ---- variant: openshift -version: 4.12.0 +version: 4.13.0 metadata: name: 99-worker-kdump <1> labels: diff --git a/modules/update-network-sysctl-allowlist.adoc b/modules/update-network-sysctl-allowlist.adoc index 6f5988912c..bea23fc7b3 100644 --- a/modules/update-network-sysctl-allowlist.adoc +++ b/modules/update-network-sysctl-allowlist.adoc @@ -48,7 +48,7 @@ metadata: annotations: kubernetes.io/description: | Sysctl allowlist for nodes. - release.openshift.io/version: 4.12.0-0.nightly-2022-11-16-003434 + release.openshift.io/version: 4.13.0-0.nightly-2022-11-16-003434 creationTimestamp: "2022-11-17T14:09:27Z" name: cni-sysctl-allowlist namespace: openshift-multus diff --git a/modules/virt-binding-devices-vfio-driver.adoc b/modules/virt-binding-devices-vfio-driver.adoc index 3a3bc8363b..c3fe65ba16 100644 --- a/modules/virt-binding-devices-vfio-driver.adoc +++ b/modules/virt-binding-devices-vfio-driver.adoc @@ -35,7 +35,7 @@ See "Creating machine configs with Butane" for information about Butane. [source,yaml] ---- variant: openshift -version: 4.12.0 +version: 4.13.0 metadata: name: 100-worker-vfiopci labels: diff --git a/modules/virt-enabling-virt-repos.adoc b/modules/virt-enabling-virt-repos.adoc index 8060aa6a7e..f466b2d043 100644 --- a/modules/virt-enabling-virt-repos.adoc +++ b/modules/virt-enabling-virt-repos.adoc @@ -20,12 +20,12 @@ Enable the {VirtProductName} repository for your version of {op-system-base-full + [source,terminal] ---- -# subscription-manager repos --enable cnv-4.12-for-rhel-8-x86_64-rpms +# subscription-manager repos --enable cnv-4.13-for-rhel-8-x86_64-rpms ---- ** To enable the repository for {op-system-base} 7, run: + [source,terminal] ---- -# subscription-manager repos --enable rhel-7-server-cnv-4.12-rpms +# subscription-manager repos --enable rhel-7-server-cnv-4.13-rpms ---- \ No newline at end of file diff --git a/modules/virt-measuring-latency-vm-secondary-network.adoc b/modules/virt-measuring-latency-vm-secondary-network.adoc index 059fb54e82..b8e71edbe8 100644 --- a/modules/virt-measuring-latency-vm-secondary-network.adoc +++ b/modules/virt-measuring-latency-vm-secondary-network.adoc @@ -140,7 +140,7 @@ spec: restartPolicy: Never containers: - name: vm-latency-checkup - image: registry.redhat.io/container-native-virtualization/vm-network-latency-checkup:v4.12.0 + image: registry.redhat.io/container-native-virtualization/vm-network-latency-checkup:v4.13.0 securityContext: allowPrivilegeEscalation: false capabilities: diff --git a/storage/container_storage_interface/osd-persistent-storage-aws-efs-csi.adoc b/storage/container_storage_interface/osd-persistent-storage-aws-efs-csi.adoc index 043714f511..8eab7664b6 100644 --- a/storage/container_storage_interface/osd-persistent-storage-aws-efs-csi.adoc +++ b/storage/container_storage_interface/osd-persistent-storage-aws-efs-csi.adoc @@ -16,7 +16,7 @@ This procedure is specific to the Amazon Web Services Elastic File System (AWS E {product-title} is capable of provisioning persistent volumes (PVs) using the Container Storage Interface (CSI) driver for AWS Elastic File Service (EFS). -Familiarity with link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.12/html-single/storage/index#persistent-storage-overview_understanding-persistent-storage[persistent storage] and link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.12/html-single/storage/index#persistent-storage-csi[configuring CSI volumes] is recommended when working with a CSI Operator and driver. +Familiarity with link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.13/html-single/storage/index#persistent-storage-overview_understanding-persistent-storage[persistent storage] and link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.13/html-single/storage/index#persistent-storage-csi[configuring CSI volumes] is recommended when working with a CSI Operator and driver. After installing the AWS EFS CSI Driver Operator, {product-title} installs the AWS EFS CSI Operator and the AWS EFS CSI driver by default in the `openshift-cluster-csi-drivers` namespace. This allows the AWS EFS CSI Driver Operator to create CSI-provisioned PVs that mount to AWS EFS assets. @@ -87,5 +87,5 @@ include::modules/persistent-storage-csi-olm-operator-uninstall.adoc[leveloffset= [role="_additional-resources"] == Additional resources -* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.12/html-single/storage/index#persistent-storage-csi[Configuring CSI volumes] +* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.13/html-single/storage/index#persistent-storage-csi[Configuring CSI volumes] diff --git a/storage/persistent_storage/rosa-persistent-storage-aws-efs-csi.adoc b/storage/persistent_storage/rosa-persistent-storage-aws-efs-csi.adoc index 211e777774..6114a53cfe 100644 --- a/storage/persistent_storage/rosa-persistent-storage-aws-efs-csi.adoc +++ b/storage/persistent_storage/rosa-persistent-storage-aws-efs-csi.adoc @@ -16,7 +16,7 @@ This procedure is specific to the Amazon Web Services Elastic File System (AWS E {product-title} is capable of provisioning persistent volumes (PVs) using the Container Storage Interface (CSI) driver for AWS Elastic File Service (EFS). -Familiarity with link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.12/html-single/storage/index#persistent-storage-overview_understanding-persistent-storage[persistent storage] and link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.12/html-single/storage/index#persistent-storage-csi[configuring CSI volumes] is recommended when working with a CSI Operator and driver. +Familiarity with link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.13/html-single/storage/index#persistent-storage-overview_understanding-persistent-storage[persistent storage] and link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.13/html-single/storage/index#persistent-storage-csi[configuring CSI volumes] is recommended when working with a CSI Operator and driver. After installing the AWS EFS CSI Driver Operator, {product-title} installs the AWS EFS CSI Operator and the AWS EFS CSI driver by default in the `openshift-cluster-csi-drivers` namespace. This allows the AWS EFS CSI Driver Operator to create CSI-provisioned PVs that mount to AWS EFS assets. @@ -51,7 +51,7 @@ include::modules/persistent-storage-csi-efs-sts.adoc[leveloffset=+1] * xref:../../storage/persistent_storage/rosa-persistent-storage-aws-efs-csi.adoc#persistent-storage-csi-olm-operator-install_rosa-persistent-storage-aws-efs-csi[Installing the AWS EFS CSI Driver Operator] -* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.12/html-single/authentication_and_authorization/index#cco-ccoctl-configuring_cco-mode-sts[Configuring the Cloud Credential Operator utility] +* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.13/html-single/authentication_and_authorization/index#cco-ccoctl-configuring_cco-mode-sts[Configuring the Cloud Credential Operator utility] :StorageClass: AWS EFS :Provisioner: efs.csi.aws.com @@ -80,5 +80,5 @@ include::modules/persistent-storage-csi-olm-operator-uninstall.adoc[leveloffset= [role="_additional-resources"] == Additional resources -* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.12/html-single/storage/index#persistent-storage-csi[Configuring CSI volumes] +* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.13/html-single/storage/index#persistent-storage-csi[Configuring CSI volumes] diff --git a/virt/support/virt-collecting-virt-data.adoc b/virt/support/virt-collecting-virt-data.adoc index ead0a1d7a1..28f5a7b1b4 100644 --- a/virt/support/virt-collecting-virt-data.adoc +++ b/virt/support/virt-collecting-virt-data.adoc @@ -34,7 +34,7 @@ Collecting data about your environment minimizes the time required to analyze an .Procedure . xref:../../support/gathering-cluster-data.adoc#support_gathering_data_gathering-cluster-data[Collect must-gather data for the cluster]. -. link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.12/html-single/troubleshooting_openshift_data_foundation/index#downloading-log-files-and-diagnostic-information_rhodf[Collect must-gather data for {rh-storage-first}], if necessary. +. link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.13/html-single/troubleshooting_openshift_data_foundation/index#downloading-log-files-and-diagnostic-information_rhodf[Collect must-gather data for {rh-storage-first}], if necessary. . xref:../../virt/support/virt-collecting-virt-data.adoc#virt-using-virt-must-gather_virt-collecting-virt-data[Collect must-gather data for {VirtProductName}]. . xref:../../monitoring/managing-metrics.adoc#querying-metrics-for-all-projects-as-an-administrator_managing-metrics[Collect Prometheus metrics for the cluster].