From 49ec7ee9154a67bfee40e0af99da6fad2854640a Mon Sep 17 00:00:00 2001 From: Andrew Taylor Date: Mon, 3 Feb 2025 08:00:31 -0500 Subject: [PATCH] OSDOCS-11309: hardcoded 4.18 version number bump --- ...an-aws-iam-role-for-a-service-account.adoc | 2 +- .../cco-mode-mint.adoc | 2 +- extensions/index.adoc | 2 +- .../planning-migration-3-4.adoc | 2 +- modules/about-developer-perspective.adoc | 2 +- modules/cpmso-openstack-with-az-config.adoc | 4 +-- modules/create-wif-cluster-cli.adoc | 20 ++++++------ ...ting-config-files-cluster-install-oci.adoc | 4 +-- modules/hcp-aws-hc-ext-dns.adoc | 2 +- modules/hcp-bm-hc-mirror.adoc | 2 +- modules/hcp-bm-hc.adoc | 2 +- modules/hcp-bm-ingress.adoc | 2 +- modules/hcp-create-hc-arm64-aws.adoc | 2 +- modules/hcp-dc-image-mirror.adoc | 8 ++--- ...hcp-ibm-z-adding-reg-ca-hostedcluster.adoc | 2 +- modules/hcp-non-bm-hc-mirror.adoc | 2 +- modules/hcp-non-bm-hc.adoc | 2 +- ...hosted-control-planes-version-support.adoc | 2 +- modules/ibi-create-iso-for-bmh.adoc | 6 ++-- .../ibi-extra-partition-ibi-install-iso.adoc | 2 +- .../insights-operator-one-time-gather.adoc | 2 +- modules/installation-arm-bootstrap.adoc | 4 +-- modules/installation-arm-control-plane.adoc | 4 +-- modules/installation-arm-dns.adoc | 4 +-- modules/installation-arm-image-storage.adoc | 4 +-- modules/installation-arm-vnet.adoc | 4 +-- modules/installation-arm-worker.adoc | 4 +-- ...installation-cloudformation-bootstrap.adoc | 2 +- ...allation-cloudformation-control-plane.adoc | 2 +- modules/installation-cloudformation-dns.adoc | 2 +- .../installation-cloudformation-security.adoc | 2 +- modules/installation-cloudformation-vpc.adoc | 2 +- .../installation-cloudformation-worker.adoc | 2 +- ...allation-deployment-manager-bootstrap.adoc | 2 +- ...tion-deployment-manager-control-plane.adoc | 2 +- ...nstallation-deployment-manager-ext-lb.adoc | 2 +- ...ion-deployment-manager-firewall-rules.adoc | 2 +- ...ion-deployment-manager-iam-shared-vpc.adoc | 2 +- ...nstallation-deployment-manager-int-lb.adoc | 2 +- ...lation-deployment-manager-private-dns.adoc | 2 +- .../installation-deployment-manager-vpc.adoc | 2 +- ...nstallation-deployment-manager-worker.adoc | 2 +- .../installation-gcp-user-infra-rhcos.adoc | 2 +- ...ation-obtaining-fips-installer-mirror.adoc | 2 +- .../installation-user-infra-machines-iso.adoc | 8 ++--- .../installation-user-infra-machines-pxe.adoc | 24 +++++++------- modules/installation-vsphere-machines.adoc | 2 +- ...ling-a-cluster-with-multiarch-support.adoc | 2 +- .../k8s-nmstate-deploying-nmstate-CLI.adoc | 2 +- modules/logging-loki-storage-odf.adoc | 2 +- ...aintained-credentials-upgrade-extract.adoc | 2 +- modules/manually-removing-cloud-creds.adoc | 2 +- modules/mirror-registry-release-notes.adoc | 2 +- .../oadp-gcp-wif-cloud-authentication.adoc | 2 +- ...c-mirror-building-image-set-config-v2.adoc | 8 ++--- .../oc-mirror-image-set-config-examples.adoc | 10 +++--- modules/oc-mirror-imageset-config-params.adoc | 8 ++--- modules/odc-accessing-perspectives.adoc | 2 +- modules/olm-catalogsource-image-template.adoc | 4 +-- modules/olmv1-adding-a-catalog.adoc | 4 +-- ...iguring-registry-storage-rhodf-cephfs.adoc | 2 +- ...guring-registry-storage-rhodf-cephrgw.adoc | 2 +- ...figuring-registry-storage-rhodf-nooba.adoc | 2 +- modules/rosa-create-objects.adoc | 2 +- ...g-account-wide-iam-roles-and-policies.adoc | 6 ++-- modules/rosa-hcp-deleting-cluster.adoc | 2 +- ...g-a-cluster-external-auth-cluster-cli.adoc | 2 +- ...account-wide-role-and-policy-commands.adoc | 2 +- ...a-sts-account-wide-roles-and-policies.adoc | 32 +++++++++---------- ...equirements-attaching-boundary-policy.adoc | 8 ++--- ...ing-a-cluster-with-customizations-cli.adoc | 4 +-- .../sd-understanding-process-id-limits.adoc | 2 +- modules/serverless-quarkus-template.adoc | 2 +- modules/telco-core-load-balancer.adoc | 2 +- modules/telco-core-rds-container.adoc | 2 +- modules/update-preparing-ack.adoc | 6 ++-- modules/using-cluster-compare-telco-ref.adoc | 2 +- ...fying-cluster-install-oci-agent-based.adoc | 6 ++-- .../virt-checking-storage-configuration.adoc | 4 +-- modules/virt-metro-dr-odf.adoc | 2 +- modules/virt-regional-dr-odf.adoc | 2 +- ...-configure-higher-vm-workload-density.adoc | 2 +- ...mage-based-upgrade-procedure-rollback.adoc | 4 +-- osd_planning/gcp-ccs.adoc | 2 +- ...onfiguring-registry-storage-baremetal.adoc | 2 +- .../configuring-registry-storage-nutanix.adoc | 2 +- .../configuring-registry-storage-rhodf.adoc | 2 +- .../configuring-registry-storage-vsphere.adoc | 2 +- snippets/ibu-ImageBasedGroupUpgrade.adoc | 4 +-- .../osd-persistent-storage-aws-efs-csi.adoc | 4 +-- .../rosa-persistent-storage-aws-efs-csi.adoc | 6 ++-- support/approved-access.adoc | 2 +- .../virt-disaster-recovery.adoc | 2 +- virt/support/virt-collecting-virt-data.adoc | 2 +- 94 files changed, 173 insertions(+), 173 deletions(-) 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 6d2d4a247e75..77eb779a2412 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 @@ -38,5 +38,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.17/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.18/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/authentication/managing_cloud_provider_credentials/cco-mode-mint.adoc b/authentication/managing_cloud_provider_credentials/cco-mode-mint.adoc index db3c5ecae040..b7bb544055db 100644 --- a/authentication/managing_cloud_provider_credentials/cco-mode-mint.adoc +++ b/authentication/managing_cloud_provider_credentials/cco-mode-mint.adoc @@ -17,7 +17,7 @@ The CCO uses the `admin` credential to process the `CredentialsRequest` objects With mint mode, each cluster component has only the specific permissions it requires. Cloud credential reconciliation is automatic and continuous so that components can perform actions that require additional credentials or permissions. -For example, a minor version cluster update (such as updating from {product-title} 4.16 to 4.17) might include an updated `CredentialsRequest` resource for a cluster component. +For example, a minor version cluster update (such as updating from {product-title} {ocp-nminus1} to {product-version}) might include an updated `CredentialsRequest` resource for a cluster component. The CCO, operating in mint mode, uses the `admin` credential to process the `CredentialsRequest` resource and create users with limited permissions to satisfy the updated authentication requirements. [NOTE] diff --git a/extensions/index.adoc b/extensions/index.adoc index 365ae5456b87..9ee0183b33d4 100644 --- a/extensions/index.adoc +++ b/extensions/index.adoc @@ -8,7 +8,7 @@ toc::[] Extensions enable cluster administrators to extend capabilities for users on their {product-title} cluster. -{olm-first} has been included with {product-title} 4 since its initial release. {product-title} 4.17 includes components for a next-generation iteration of {olm} as a Generally Available (GA) feature, known during this phase as _{olmv1}_. This updated framework evolves many of the concepts that have been part of previous versions of {olm} and adds new capabilities. +{olm-first} has been included with {product-title} 4 since its initial release. {product-title} {product-verison} includes components for a next-generation iteration of {olm} as a Generally Available (GA) feature, known during this phase as _{olmv1}_. This updated framework evolves many of the concepts that have been part of previous versions of {olm} and adds new capabilities. [id="olmv1-highlights_{context}"] == Highlights diff --git a/migrating_from_ocp_3_to_4/planning-migration-3-4.adoc b/migrating_from_ocp_3_to_4/planning-migration-3-4.adoc index 7b9c7a5a62f9..f7e48580603b 100644 --- a/migrating_from_ocp_3_to_4/planning-migration-3-4.adoc +++ b/migrating_from_ocp_3_to_4/planning-migration-3-4.adoc @@ -180,7 +180,7 @@ For information on OVN-Kubernetes features that are similar to features in the O [WARNING] ==== -You should install {product-title} 4 with the OVN-Kubernetes network plugin because it is not possible to upgrade a cluster to {product-title} 4.17 if it is using the OpenShift SDN network plugin. +You should install {product-title} 4 with the OVN-Kubernetes network plugin because it is not possible to upgrade a cluster to {product-title} 4.17 or later if it is using the OpenShift SDN network plugin. ==== [id="migration-preparing-logging"] diff --git a/modules/about-developer-perspective.adoc b/modules/about-developer-perspective.adoc index 22cea552cb2f..a131d71c8d16 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.17/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.18/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/cpmso-openstack-with-az-config.adoc b/modules/cpmso-openstack-with-az-config.adoc index bff22f5c59e5..5e1c70c57fa1 100644 --- a/modules/cpmso-openstack-with-az-config.adoc +++ b/modules/cpmso-openstack-with-az-config.adoc @@ -32,7 +32,7 @@ where: . For the `master-1` and `master-2` control plane machines, edit the value of the `serverGroupName` property in their provider specs to match that of the machine `master-0`. + .An example {rh-openstack} provider spec -[source,yaml] +[source,yaml,subs="attributes+"] ---- providerSpec: value: @@ -43,7 +43,7 @@ providerSpec: name: openstack-cloud-credentials namespace: openshift-machine-api flavor: m1.xlarge - image: rhcos-4.17 + image: rhcos-{product-version} kind: OpenstackProviderSpec metadata: creationTimestamp: null diff --git a/modules/create-wif-cluster-cli.adoc b/modules/create-wif-cluster-cli.adoc index a35fbafcbb55..c8f978bd045b 100644 --- a/modules/create-wif-cluster-cli.adoc +++ b/modules/create-wif-cluster-cli.adoc @@ -59,7 +59,7 @@ $ ocm gcp create wif-config --name \ <1> 2024/09/26 13:05:52 IAM service account cloud-credential-operator-oeub created 2024/09/26 13:05:52 IAM service account openshift-cloud-network-c-oeub created 2024/09/26 13:05:53 IAM service account openshift-ingress-gcp-oeub created -2024/09/26 13:05:55 Role "osd_deployer_v4.17" updated +2024/09/26 13:05:55 Role "osd_deployer_v4.18" updated ---- -- + @@ -85,7 +85,7 @@ Once the WIF is configured, the following service accounts, roles, and groups ar |osd-deployer -|osd_deployer_v4.17 +|osd_deployer_v4.18 |osd-control-plane @@ -99,35 +99,35 @@ Once the WIF is configured, the following service accounts, roles, and groups ar - compute.viewer |cloud-credential-operator-gcp-ro-creds -|cloud_credential_operator_gcp_ro_creds_v4.17 +|cloud_credential_operator_gcp_ro_creds_v{product-version} |openshift-cloud-network-config-controller-gcp -|openshift_cloud_network_config_controller_gcp_v4.17 +|openshift_cloud_network_config_controller_gcp_v{product-version} |openshift-gcp-ccm -|openshift_gcp_ccm_v4.17 +|openshift_gcp_ccm_v{product-version} |openshift-gcp-pd-csi-driver-operator |- compute.storageAdmin - iam.serviceAccountUser - resourcemanager.tagUser -- openshift_gcp_pd_csi_driver_operator_v4.17 +- openshift_gcp_pd_csi_driver_operator_v{product-version} |openshift-image-registry-gcp -|openshift_image_registry_gcs_v4.17 +|openshift_image_registry_gcs_v{product-version} |openshift-ingress-gcp -|openshift_ingress_gcp_v4.17 +|openshift_ingress_gcp_v{product-version} |openshift-machine-api-gcp -|openshift_machine_api_gcp_v4.17 +|openshift_machine_api_gcp_v{product-version} |Access via SRE group:sd-sre-platform-gcp-access |sre_managed_support |=== -For further details about WIF configuration roles and their assigned permissions, see link:https://github.com/openshift/managed-cluster-config/blob/master/resources/wif/4.17/vanilla.yaml[managed-cluster-config]. +For further details about WIF configuration roles and their assigned permissions, see link:https://github.com/openshift/managed-cluster-config/blob/master/resources/wif/4.18/vanilla.yaml[managed-cluster-config]. [id="create-wif-cluster_{context}"] == Creating a WIF cluster diff --git a/modules/creating-config-files-cluster-install-oci.adoc b/modules/creating-config-files-cluster-install-oci.adoc index cc3163eb56e9..68d76d80e229 100644 --- a/modules/creating-config-files-cluster-install-oci.adoc +++ b/modules/creating-config-files-cluster-install-oci.adoc @@ -34,9 +34,9 @@ $ ./openshift-install version .Example output for a shared registry binary [source,terminal,subs="quotes"] ---- -./openshift-install 4.17.0 +./openshift-install 4.18.0 built from commit ae7977b7d1ca908674a0d45c5c243c766fa4b2ca -release image registry.ci.openshift.org/origin/release:4.17ocp-release@sha256:0da6316466d60a3a4535d5fed3589feb0391989982fba59d47d4c729912d6363 +release image registry.ci.openshift.org/origin/release:4.18ocp-release@sha256:0da6316466d60a3a4535d5fed3589feb0391989982fba59d47d4c729912d6363 release architecture amd64 ---- ==== diff --git a/modules/hcp-aws-hc-ext-dns.adoc b/modules/hcp-aws-hc-ext-dns.adoc index 58e5c7e5b7a1..fb7185bad3a2 100644 --- a/modules/hcp-aws-hc-ext-dns.adoc +++ b/modules/hcp-aws-hc-ext-dns.adoc @@ -64,7 +64,7 @@ $ hcp create cluster aws \ <5> Specify the public hosted zone that the service consumer owns, for example, `service-consumer-domain.com`. <6> Specify the node replica count, for example, `2`. <7> Specify the path to your pull secret file. -<8> Specify the supported {product-title} version that you want to use, for example, `4.17.0-multi`. +<8> Specify the supported {product-title} version that you want to use, for example, `4.18.0-multi`. <9> Specify the public hosted zone that the service provider owns, for example, `service-provider-domain.com`. <10> Set as `PublicAndPrivate`. You can use external DNS with `Public` or `PublicAndPrivate` configurations only. <11> Specify the path to your {aws-short} STS credentials file, for example, `/home/user/sts-creds/sts-creds.json`. \ No newline at end of file diff --git a/modules/hcp-bm-hc-mirror.adoc b/modules/hcp-bm-hc-mirror.adoc index 6c5b1515e425..0248b7c692f1 100644 --- a/modules/hcp-bm-hc-mirror.adoc +++ b/modules/hcp-bm-hc-mirror.adoc @@ -52,4 +52,4 @@ $ hcp create cluster agent \ <6> Specify the `icsp.yaml` file that defines ICSP and your mirror registries. <7> Specify the path to your SSH public key. The default file path is `~/.ssh/id_rsa.pub`. <8> Specify your hosted cluster namespace. -<9> Specify the supported {product-title} version that you want to use, for example, `4.17.0-multi`. If you are using a disconnected environment, replace `` with the digest image. To extract the {product-title} release image digest, see _Extracting the {product-title} release image digest_. \ No newline at end of file +<9> Specify the supported {product-title} version that you want to use, for example, `4.18.0-multi`. If you are using a disconnected environment, replace `` with the digest image. To extract the {product-title} release image digest, see _Extracting the {product-title} release image digest_. \ No newline at end of file diff --git a/modules/hcp-bm-hc.adoc b/modules/hcp-bm-hc.adoc index 819c8449da59..5ab5afcf1837 100644 --- a/modules/hcp-bm-hc.adoc +++ b/modules/hcp-bm-hc.adoc @@ -58,7 +58,7 @@ $ hcp create cluster agent \ <7> Specify the path to your SSH public key. The default file path is `~/.ssh/id_rsa.pub`. <8> Specify your hosted cluster namespace. <9> Specify the availability policy for the hosted control plane components. Supported options are `SingleReplica` and `HighlyAvailable`. The default value is `HighlyAvailable`. -<10> Specify the supported {product-title} version that you want to use, for example, `4.17.0-multi`. If you are using a disconnected environment, replace `` with the digest image. To extract the {product-title} release image digest, see _Extracting the {product-title} release image digest_. +<10> Specify the supported {product-title} version that you want to use, for example, `4.18.0-multi`. If you are using a disconnected environment, replace `` with the digest image. To extract the {product-title} release image digest, see _Extracting the {product-title} release image digest_. <11> Specify the node pool replica count, for example, `3`. You must specify the replica count as `0` or greater to create the same number of replicas. Otherwise, no node pools are created. + diff --git a/modules/hcp-bm-ingress.adoc b/modules/hcp-bm-ingress.adoc index 99614a9887c9..0d5fa38ad25b 100644 --- a/modules/hcp-bm-ingress.adoc +++ b/modules/hcp-bm-ingress.adoc @@ -204,7 +204,7 @@ clusteroperator.config.openshift.io/console clusteroperator.config.openshift.io/ingress 4.x.y True False False 53m ---- + -Replace `<4.x.y>` with the supported {product-title} version that you want to use, for example, `4.17.0-multi`. +Replace `<4.x.y>` with the supported {product-title} version that you want to use, for example, `4.18.0-multi`. ifeval::["{context}" == "hcp-manage-non-bm"] diff --git a/modules/hcp-create-hc-arm64-aws.adoc b/modules/hcp-create-hc-arm64-aws.adoc index 4e4ffbb6a8d0..87a9f0a99038 100644 --- a/modules/hcp-create-hc-arm64-aws.adoc +++ b/modules/hcp-create-hc-arm64-aws.adoc @@ -37,7 +37,7 @@ $ hcp create cluster aws \ <4> Specify the path to your pull secret, for example, `/user/name/pullsecret`. <5> Specify the path to your AWS STS credentials file, for example, `/home/user/sts-creds/sts-creds.json`. <6> Specify the AWS region name, for example, `us-east-1`. -<7> Specify the supported {product-title} version that you want to use, for example, `4.17.0-multi`. If you are using a disconnected environment, replace `` with the digest image. To extract the {product-title} release image digest, see "Extracting the {product-title} release image digest". +<7> Specify the supported {product-title} version that you want to use, for example, `4.18.0-multi`. If you are using a disconnected environment, replace `` with the digest image. To extract the {product-title} release image digest, see "Extracting the {product-title} release image digest". <8> Specify the Amazon Resource Name (ARN), for example, `arn:aws:iam::820196288204:role/myrole`. . Add a `NodePool` object to the hosted cluster by running the following command: diff --git a/modules/hcp-dc-image-mirror.adoc b/modules/hcp-dc-image-mirror.adoc index 673cd911b6b0..09a09565d4b1 100644 --- a/modules/hcp-dc-image-mirror.adoc +++ b/modules/hcp-dc-image-mirror.adoc @@ -27,7 +27,7 @@ To configure image mirroring, complete the following steps: . By using the following example, create an `ImageSetConfiguration` object to use for mirroring. Replace values as needed to match your environment: + -[source,yaml] +[source,yaml,subs="attributes+"] ---- apiVersion: mirror.openshift.io/v1alpha2 kind: ImageSetConfiguration @@ -37,7 +37,7 @@ storageConfig: mirror: platform: channels: - - name: candidate-4.17 + - name: candidate-{product-version} minVersion: <4.x.y-build> <2> maxVersion: <4.x.y-build> <2> type: ocp @@ -52,10 +52,10 @@ mirror: - name: quay.io/karmab/curl:latest - name: quay.io/karmab/kcli:latest - name: quay.io/user-name/trbsht:latest - - name: quay.io/user-name/hypershift:BMSelfManage-v4.17 + - name: quay.io/user-name/hypershift:BMSelfManage-v{product-version} - name: registry.redhat.io/openshift4/ose-kube-rbac-proxy:v4.10 operators: - - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.17 + - catalog: registry.redhat.io/redhat/redhat-operator-index:v{product-version} packages: - name: lvms-operator - name: local-storage-operator diff --git a/modules/hcp-ibm-z-adding-reg-ca-hostedcluster.adoc b/modules/hcp-ibm-z-adding-reg-ca-hostedcluster.adoc index 9736b400b3f4..1fe8647721bc 100644 --- a/modules/hcp-ibm-z-adding-reg-ca-hostedcluster.adoc +++ b/modules/hcp-ibm-z-adding-reg-ca-hostedcluster.adoc @@ -44,5 +44,5 @@ $ hcp create cluster agent \ <4> Replace the name with your base domain, for example, `example.com`. <5> Replace the etcd storage class name, for example, `lvm-storageclass`. <6> Replace the path to your SSH public key. The default file path is `~/.ssh/id_rsa.pub`. -<7> Replace with the supported {product-title} version that you want to use, for example, `4.17.0-multi`. +<7> Replace with the supported {product-title} version that you want to use, for example, `4.18.0-multi`. <8> Replace the path to Certificate Authority of mirror registry. \ No newline at end of file diff --git a/modules/hcp-non-bm-hc-mirror.adoc b/modules/hcp-non-bm-hc-mirror.adoc index 61ec22e3e46e..e57f990c4cbf 100644 --- a/modules/hcp-non-bm-hc-mirror.adoc +++ b/modules/hcp-non-bm-hc-mirror.adoc @@ -52,4 +52,4 @@ $ hcp create cluster agent \ <6> Specify the `icsp.yaml` file that defines ICSP and your mirror registries. <7> Specify the path to your SSH public key. The default file path is `~/.ssh/id_rsa.pub`. <8> Specify your hosted cluster namespace. -<9> Specify the supported {product-title} version that you want to use, for example, `4.17.0-multi`. If you are using a disconnected environment, replace `` with the digest image. To extract the {product-title} release image digest, see _Extracting the {product-title} release image digest_. +<9> Specify the supported {product-title} version that you want to use, for example, `4.18.0-multi`. If you are using a disconnected environment, replace `` with the digest image. To extract the {product-title} release image digest, see _Extracting the {product-title} release image digest_. diff --git a/modules/hcp-non-bm-hc.adoc b/modules/hcp-non-bm-hc.adoc index 9d846bc48e72..de7d24aff0dc 100644 --- a/modules/hcp-non-bm-hc.adoc +++ b/modules/hcp-non-bm-hc.adoc @@ -54,7 +54,7 @@ $ hcp create cluster agent \ <7> Specify the path to your SSH public key. The default file path is `~/.ssh/id_rsa.pub`. <8> Specify your hosted cluster namespace. <9> Specify the availability policy for the hosted control plane components. Supported options are `SingleReplica` and `HighlyAvailable`. The default value is `HighlyAvailable`. -<10> Specify the supported {product-title} version that you want to use, for example, `4.17.0-multi`. +<10> Specify the supported {product-title} version that you want to use, for example, `4.18.0-multi`. <11> Specify the node pool replica count, for example, `3`. You must specify the replica count as `0` or greater to create the same number of replicas. Otherwise, no node pools are created. .Verification diff --git a/modules/hosted-control-planes-version-support.adoc b/modules/hosted-control-planes-version-support.adoc index 8c18fc3c79ea..85dae5aba3ff 100644 --- a/modules/hosted-control-planes-version-support.adoc +++ b/modules/hosted-control-planes-version-support.adoc @@ -43,7 +43,7 @@ You can host different versions of control planes on the same management cluster ---- apiVersion: v1 data: - supported-versions: '{"versions":["4.17"]}' + supported-versions: '{"versions":["4.18"]}' kind: ConfigMap metadata: labels: diff --git a/modules/ibi-create-iso-for-bmh.adoc b/modules/ibi-create-iso-for-bmh.adoc index 083e0960c6db..fde75f19d9f7 100644 --- a/modules/ibi-create-iso-for-bmh.adoc +++ b/modules/ibi-create-iso-for-bmh.adoc @@ -59,8 +59,8 @@ kind: ImageBasedInstallationConfig metadata: name: example-image-based-installation-config # The following fields are required -seedImage: quay.io/openshift-kni/seed-image:4.17.0 -seedVersion: 4.17.0 +seedImage: quay.io/openshift-kni/seed-image:4.18.0 +seedVersion: 4.18.0 installationDisk: /dev/vda pullSecret: '' # networkConfig is optional and contains the network configuration for the host in NMState format. @@ -89,7 +89,7 @@ kind: ImageBasedInstallationConfig metadata: name: example-image-based-installation-config seedImage: quay.io/repo-id/seed:latest -seedVersion: "4.17.0" +seedVersion: "4.18.0" extraPartitionStart: "-240G" installationDisk: /dev/disk/by-id/wwn-0x62c... sshKey: 'ssh-ed25519 AAAA...' diff --git a/modules/ibi-extra-partition-ibi-install-iso.adoc b/modules/ibi-extra-partition-ibi-install-iso.adoc index a11ab8496c0b..2a32591c8cf6 100644 --- a/modules/ibi-extra-partition-ibi-install-iso.adoc +++ b/modules/ibi-extra-partition-ibi-install-iso.adoc @@ -27,7 +27,7 @@ kind: ImageBasedInstallationConfig metadata: name: example-extra-partition seedImage: quay.io/repo-id/seed:latest -seedVersion: "4.17.0" +seedVersion: "4.18.0" installationDisk: /dev/sda pullSecret: '{"auths": ...}' # ... diff --git a/modules/insights-operator-one-time-gather.adoc b/modules/insights-operator-one-time-gather.adoc index 58b68ee6f24c..810bcc8602da 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.17/docs/gather-job.yaml[] +include::https://raw.githubusercontent.com/openshift/insights-operator/release-4.18/docs/gather-job.yaml[] ---- . Copy your `insights-operator` image version: + diff --git a/modules/installation-arm-bootstrap.adoc b/modules/installation-arm-bootstrap.adoc index 192dfecc8368..db9f76bab32c 100644 --- a/modules/installation-arm-bootstrap.adoc +++ b/modules/installation-arm-bootstrap.adoc @@ -20,10 +20,10 @@ bootstrap machine that you need for your {product-title} cluster: [source,json] ---- ifndef::ash[] -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/azure/04_bootstrap.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/azure/04_bootstrap.json[] endif::ash[] ifdef::ash[] -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/azurestack/04_bootstrap.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/azurestack/04_bootstrap.json[] endif::ash[] ---- ==== diff --git a/modules/installation-arm-control-plane.adoc b/modules/installation-arm-control-plane.adoc index 249f3058d044..cff1aa1151f5 100644 --- a/modules/installation-arm-control-plane.adoc +++ b/modules/installation-arm-control-plane.adoc @@ -20,10 +20,10 @@ control plane machines that you need for your {product-title} cluster: [source,json] ---- ifndef::ash[] -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/azure/05_masters.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/azure/05_masters.json[] endif::ash[] ifdef::ash[] -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/azurestack/05_masters.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/azurestack/05_masters.json[] endif::ash[] ---- ==== diff --git a/modules/installation-arm-dns.adoc b/modules/installation-arm-dns.adoc index f028c422011a..6ae936edef86 100644 --- a/modules/installation-arm-dns.adoc +++ b/modules/installation-arm-dns.adoc @@ -21,10 +21,10 @@ cluster: [source,json] ---- ifndef::ash[] -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/azure/03_infra.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/azure/03_infra.json[] endif::ash[] ifdef::ash[] -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/azurestack/03_infra.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/azurestack/03_infra.json[] endif::ash[] ---- ==== diff --git a/modules/installation-arm-image-storage.adoc b/modules/installation-arm-image-storage.adoc index f06a2fd3b88e..775e9175ec0b 100644 --- a/modules/installation-arm-image-storage.adoc +++ b/modules/installation-arm-image-storage.adoc @@ -20,10 +20,10 @@ stored {op-system-first} image that you need for your {product-title} cluster: [source,json] ---- ifndef::ash[] -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/azure/02_storage.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/azure/02_storage.json[] endif::ash[] ifdef::ash[] -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/azurestack/02_storage.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/azurestack/02_storage.json[] endif::ash[] ---- ==== diff --git a/modules/installation-arm-vnet.adoc b/modules/installation-arm-vnet.adoc index d859ce692406..868d0df1f5f0 100644 --- a/modules/installation-arm-vnet.adoc +++ b/modules/installation-arm-vnet.adoc @@ -20,10 +20,10 @@ VNet that you need for your {product-title} cluster: [source,json] ---- ifndef::ash[] -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/azure/01_vnet.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/azure/01_vnet.json[] endif::ash[] ifdef::ash[] -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/azurestack/01_vnet.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/azurestack/01_vnet.json[] endif::ash[] ---- ==== diff --git a/modules/installation-arm-worker.adoc b/modules/installation-arm-worker.adoc index 5273765e8989..4f9e2849f1a9 100644 --- a/modules/installation-arm-worker.adoc +++ b/modules/installation-arm-worker.adoc @@ -20,10 +20,10 @@ worker machines that you need for your {product-title} cluster: [source,json] ---- ifndef::ash[] -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/azure/06_workers.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/azure/06_workers.json[] endif::ash[] ifdef::ash[] -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/azurestack/06_workers.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/azurestack/06_workers.json[] endif::ash[] ---- ==== diff --git a/modules/installation-cloudformation-bootstrap.adoc b/modules/installation-cloudformation-bootstrap.adoc index db704f6dd6e1..dda517113a9b 100644 --- a/modules/installation-cloudformation-bootstrap.adoc +++ b/modules/installation-cloudformation-bootstrap.adoc @@ -13,6 +13,6 @@ You can use the following CloudFormation template to deploy the bootstrap machin ==== [source,yaml] ---- -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/aws/cloudformation/04_cluster_bootstrap.yaml[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/aws/cloudformation/04_cluster_bootstrap.yaml[] ---- ==== diff --git a/modules/installation-cloudformation-control-plane.adoc b/modules/installation-cloudformation-control-plane.adoc index 1489c1e6875a..f719347ccb0e 100644 --- a/modules/installation-cloudformation-control-plane.adoc +++ b/modules/installation-cloudformation-control-plane.adoc @@ -14,6 +14,6 @@ machines that you need for your {product-title} cluster. ==== [source,yaml] ---- -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/aws/cloudformation/05_cluster_master_nodes.yaml[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/aws/cloudformation/05_cluster_master_nodes.yaml[] ---- ==== diff --git a/modules/installation-cloudformation-dns.adoc b/modules/installation-cloudformation-dns.adoc index 5fde9b4e2a08..8b4a8a365a9b 100644 --- a/modules/installation-cloudformation-dns.adoc +++ b/modules/installation-cloudformation-dns.adoc @@ -14,7 +14,7 @@ objects and load balancers that you need for your {product-title} cluster. ==== [source,yaml] ---- -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/aws/cloudformation/02_cluster_infra.yaml[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/aws/cloudformation/02_cluster_infra.yaml[] ---- ==== diff --git a/modules/installation-cloudformation-security.adoc b/modules/installation-cloudformation-security.adoc index 22f159112da0..8d6c2c24ab76 100644 --- a/modules/installation-cloudformation-security.adoc +++ b/modules/installation-cloudformation-security.adoc @@ -14,6 +14,6 @@ that you need for your {product-title} cluster. ==== [source,yaml] ---- -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/aws/cloudformation/03_cluster_security.yaml[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/aws/cloudformation/03_cluster_security.yaml[] ---- ==== diff --git a/modules/installation-cloudformation-vpc.adoc b/modules/installation-cloudformation-vpc.adoc index 6c62f193a709..a8775a950b43 100644 --- a/modules/installation-cloudformation-vpc.adoc +++ b/modules/installation-cloudformation-vpc.adoc @@ -14,6 +14,6 @@ you need for your {product-title} cluster. ==== [source,yaml] ---- -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/aws/cloudformation/01_vpc.yaml[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/aws/cloudformation/01_vpc.yaml[] ---- ==== diff --git a/modules/installation-cloudformation-worker.adoc b/modules/installation-cloudformation-worker.adoc index b0732a4c3008..c3279e6e6472 100644 --- a/modules/installation-cloudformation-worker.adoc +++ b/modules/installation-cloudformation-worker.adoc @@ -14,6 +14,6 @@ that you need for your {product-title} cluster. ==== [source,yaml] ---- -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/aws/cloudformation/06_cluster_worker_node.yaml[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/aws/cloudformation/06_cluster_worker_node.yaml[] ---- ==== diff --git a/modules/installation-deployment-manager-bootstrap.adoc b/modules/installation-deployment-manager-bootstrap.adoc index 326202be007e..83baa4935303 100644 --- a/modules/installation-deployment-manager-bootstrap.adoc +++ b/modules/installation-deployment-manager-bootstrap.adoc @@ -14,6 +14,6 @@ machine that you need for your {product-title} cluster: ==== [source,python] ---- -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/gcp/04_bootstrap.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/gcp/04_bootstrap.py[] ---- ==== diff --git a/modules/installation-deployment-manager-control-plane.adoc b/modules/installation-deployment-manager-control-plane.adoc index e6a4dde8fa9b..fb55d64281b5 100644 --- a/modules/installation-deployment-manager-control-plane.adoc +++ b/modules/installation-deployment-manager-control-plane.adoc @@ -14,6 +14,6 @@ plane machines that you need for your {product-title} cluster: ==== [source,python] ---- -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/gcp/05_control_plane.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/gcp/05_control_plane.py[] ---- ==== diff --git a/modules/installation-deployment-manager-ext-lb.adoc b/modules/installation-deployment-manager-ext-lb.adoc index 1c6fc20e9849..4e315147bf8b 100644 --- a/modules/installation-deployment-manager-ext-lb.adoc +++ b/modules/installation-deployment-manager-ext-lb.adoc @@ -12,6 +12,6 @@ You can use the following Deployment Manager template to deploy the external loa ==== [source,python] ---- -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/gcp/02_lb_ext.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/gcp/02_lb_ext.py[] ---- ==== diff --git a/modules/installation-deployment-manager-firewall-rules.adoc b/modules/installation-deployment-manager-firewall-rules.adoc index 5625e3a00c8f..3d7098ecc1c7 100644 --- a/modules/installation-deployment-manager-firewall-rules.adoc +++ b/modules/installation-deployment-manager-firewall-rules.adoc @@ -12,6 +12,6 @@ You can use the following Deployment Manager template to deploy the firewall rue ==== [source,python] ---- -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/gcp/03_firewall.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/gcp/03_firewall.py[] ---- ==== diff --git a/modules/installation-deployment-manager-iam-shared-vpc.adoc b/modules/installation-deployment-manager-iam-shared-vpc.adoc index 7f457589d881..95ece6be766d 100644 --- a/modules/installation-deployment-manager-iam-shared-vpc.adoc +++ b/modules/installation-deployment-manager-iam-shared-vpc.adoc @@ -12,6 +12,6 @@ You can use the following Deployment Manager template to deploy the IAM roles th ==== [source,python] ---- -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/gcp/03_iam.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/gcp/03_iam.py[] ---- ==== diff --git a/modules/installation-deployment-manager-int-lb.adoc b/modules/installation-deployment-manager-int-lb.adoc index 2a129b382e99..0da183704c61 100644 --- a/modules/installation-deployment-manager-int-lb.adoc +++ b/modules/installation-deployment-manager-int-lb.adoc @@ -12,7 +12,7 @@ You can use the following Deployment Manager template to deploy the internal loa ==== [source,python] ---- -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/gcp/02_lb_int.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/gcp/02_lb_int.py[] ---- ==== diff --git a/modules/installation-deployment-manager-private-dns.adoc b/modules/installation-deployment-manager-private-dns.adoc index 22da7f208b4a..37f2b0180e94 100644 --- a/modules/installation-deployment-manager-private-dns.adoc +++ b/modules/installation-deployment-manager-private-dns.adoc @@ -12,6 +12,6 @@ You can use the following Deployment Manager template to deploy the private DNS ==== [source,python] ---- -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/gcp/02_dns.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/gcp/02_dns.py[] ---- ==== diff --git a/modules/installation-deployment-manager-vpc.adoc b/modules/installation-deployment-manager-vpc.adoc index 38fd0ff934c6..822f49ce202e 100644 --- a/modules/installation-deployment-manager-vpc.adoc +++ b/modules/installation-deployment-manager-vpc.adoc @@ -14,6 +14,6 @@ you need for your {product-title} cluster: ==== [source,python] ---- -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/gcp/01_vpc.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/gcp/01_vpc.py[] ---- ==== diff --git a/modules/installation-deployment-manager-worker.adoc b/modules/installation-deployment-manager-worker.adoc index a60fb60712df..dc4afd5e52f8 100644 --- a/modules/installation-deployment-manager-worker.adoc +++ b/modules/installation-deployment-manager-worker.adoc @@ -14,6 +14,6 @@ that you need for your {product-title} cluster: ==== [source,python] ---- -include::https://raw.githubusercontent.com/openshift/installer/release-4.17/upi/gcp/06_worker.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/gcp/06_worker.py[] ---- ==== diff --git a/modules/installation-gcp-user-infra-rhcos.adoc b/modules/installation-gcp-user-infra-rhcos.adoc index 0c74b2e52569..3be7ef1f3524 100644 --- a/modules/installation-gcp-user-infra-rhcos.adoc +++ b/modules/installation-gcp-user-infra-rhcos.adoc @@ -12,7 +12,7 @@ your {product-title} nodes. .Procedure ifndef::openshift-origin[] -. Obtain the {op-system} image from the link:https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/4.17/[{op-system} image mirror] page. +. Obtain the {op-system} image from the link:https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/4.18/[{op-system} image mirror] page. + [IMPORTANT] ==== diff --git a/modules/installation-obtaining-fips-installer-mirror.adoc b/modules/installation-obtaining-fips-installer-mirror.adoc index b91e26c6f53a..3cfe43de57dc 100644 --- a/modules/installation-obtaining-fips-installer-mirror.adoc +++ b/modules/installation-obtaining-fips-installer-mirror.adoc @@ -13,7 +13,7 @@ .Procedure -. Download the installation program from https://mirror.openshift.com/pub/openshift-v4/clients/ocp/latest-4.17/openshift-install-rhel9-amd64.tar.gz. +. Download the installation program from https://mirror.openshift.com/pub/openshift-v4/clients/ocp/latest-4.18/openshift-install-rhel9-amd64.tar.gz. . Extract the installation program. For example, on a computer that uses a Linux operating system, run the following command: + [source,terminal] diff --git a/modules/installation-user-infra-machines-iso.adoc b/modules/installation-user-infra-machines-iso.adoc index 25c27ab9d5bb..72e8697e7e66 100644 --- a/modules/installation-user-infra-machines-iso.adoc +++ b/modules/installation-user-infra-machines-iso.adoc @@ -85,10 +85,10 @@ $ openshift-install coreos print-stream-json | grep '\.iso[^.]' [source,terminal] ifndef::openshift-origin[] ---- -"location": "/art/storage/releases/rhcos-4.17-aarch64//aarch64/rhcos--live.aarch64.iso", -"location": "/art/storage/releases/rhcos-4.17-ppc64le//ppc64le/rhcos--live.ppc64le.iso", -"location": "/art/storage/releases/rhcos-4.17-s390x//s390x/rhcos--live.s390x.iso", -"location": "/art/storage/releases/rhcos-4.17//x86_64/rhcos--live.x86_64.iso", +"location": "/art/storage/releases/rhcos-4.18-aarch64//aarch64/rhcos--live.aarch64.iso", +"location": "/art/storage/releases/rhcos-4.18-ppc64le//ppc64le/rhcos--live.ppc64le.iso", +"location": "/art/storage/releases/rhcos-4.18-s390x//s390x/rhcos--live.s390x.iso", +"location": "/art/storage/releases/rhcos-4.18//x86_64/rhcos--live.x86_64.iso", ---- endif::openshift-origin[] ifdef::openshift-origin[] diff --git a/modules/installation-user-infra-machines-pxe.adoc b/modules/installation-user-infra-machines-pxe.adoc index 4efac2c4d007..c572d99b1ca0 100644 --- a/modules/installation-user-infra-machines-pxe.adoc +++ b/modules/installation-user-infra-machines-pxe.adoc @@ -101,18 +101,18 @@ $ openshift-install coreos print-stream-json | grep -Eo '"https.*(kernel-|initra [source,terminal] ifndef::openshift-origin[] ---- -"/art/storage/releases/rhcos-4.17-aarch64//aarch64/rhcos--live-kernel-aarch64" -"/art/storage/releases/rhcos-4.17-aarch64//aarch64/rhcos--live-initramfs.aarch64.img" -"/art/storage/releases/rhcos-4.17-aarch64//aarch64/rhcos--live-rootfs.aarch64.img" -"/art/storage/releases/rhcos-4.17-ppc64le/49.84.202110081256-0/ppc64le/rhcos--live-kernel-ppc64le" -"/art/storage/releases/rhcos-4.17-ppc64le//ppc64le/rhcos--live-initramfs.ppc64le.img" -"/art/storage/releases/rhcos-4.17-ppc64le//ppc64le/rhcos--live-rootfs.ppc64le.img" -"/art/storage/releases/rhcos-4.17-s390x//s390x/rhcos--live-kernel-s390x" -"/art/storage/releases/rhcos-4.17-s390x//s390x/rhcos--live-initramfs.s390x.img" -"/art/storage/releases/rhcos-4.17-s390x//s390x/rhcos--live-rootfs.s390x.img" -"/art/storage/releases/rhcos-4.17//x86_64/rhcos--live-kernel-x86_64" -"/art/storage/releases/rhcos-4.17//x86_64/rhcos--live-initramfs.x86_64.img" -"/art/storage/releases/rhcos-4.17//x86_64/rhcos--live-rootfs.x86_64.img" +"/art/storage/releases/rhcos-4.18-aarch64//aarch64/rhcos--live-kernel-aarch64" +"/art/storage/releases/rhcos-4.18-aarch64//aarch64/rhcos--live-initramfs.aarch64.img" +"/art/storage/releases/rhcos-4.18-aarch64//aarch64/rhcos--live-rootfs.aarch64.img" +"/art/storage/releases/rhcos-4.18-ppc64le/49.84.202110081256-0/ppc64le/rhcos--live-kernel-ppc64le" +"/art/storage/releases/rhcos-4.18-ppc64le//ppc64le/rhcos--live-initramfs.ppc64le.img" +"/art/storage/releases/rhcos-4.18-ppc64le//ppc64le/rhcos--live-rootfs.ppc64le.img" +"/art/storage/releases/rhcos-4.18-s390x//s390x/rhcos--live-kernel-s390x" +"/art/storage/releases/rhcos-4.18-s390x//s390x/rhcos--live-initramfs.s390x.img" +"/art/storage/releases/rhcos-4.18-s390x//s390x/rhcos--live-rootfs.s390x.img" +"/art/storage/releases/rhcos-4.18//x86_64/rhcos--live-kernel-x86_64" +"/art/storage/releases/rhcos-4.18//x86_64/rhcos--live-initramfs.x86_64.img" +"/art/storage/releases/rhcos-4.18//x86_64/rhcos--live-rootfs.x86_64.img" ---- endif::openshift-origin[] ifdef::openshift-origin[] diff --git a/modules/installation-vsphere-machines.adoc b/modules/installation-vsphere-machines.adoc index 1f088fc2f097..0c0b7765779c 100644 --- a/modules/installation-vsphere-machines.adoc +++ b/modules/installation-vsphere-machines.adoc @@ -79,7 +79,7 @@ If you plan to add more compute machines to your cluster after you finish instal ==== ifndef::openshift-origin[] -. Obtain the {op-system} OVA image. Images are available from the link:https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/4.17/[{op-system} image mirror] page. +. Obtain the {op-system} OVA image. Images are available from the link:https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/4.18/[{op-system} image mirror] page. + [IMPORTANT] ==== diff --git a/modules/installing-a-cluster-with-multiarch-support.adoc b/modules/installing-a-cluster-with-multiarch-support.adoc index c0d9631ec3a3..1204f05478bf 100644 --- a/modules/installing-a-cluster-with-multiarch-support.adoc +++ b/modules/installing-a-cluster-with-multiarch-support.adoc @@ -22,7 +22,7 @@ $ ./openshift-install version .Example output [source,terminal] ---- -./openshift-install 4.17.0 +./openshift-install 4.18.0 built from commit abc123etc release image quay.io/openshift-release-dev/ocp-release@sha256:abc123wxyzetc release architecture multi diff --git a/modules/k8s-nmstate-deploying-nmstate-CLI.adoc b/modules/k8s-nmstate-deploying-nmstate-CLI.adoc index 1eac99c32a37..6d867522460a 100644 --- a/modules/k8s-nmstate-deploying-nmstate-CLI.adoc +++ b/modules/k8s-nmstate-deploying-nmstate-CLI.adoc @@ -77,7 +77,7 @@ $ oc get clusterserviceversion -n openshift-nmstate \ [source, terminal,subs="attributes+"] ---- Name Phase -kubernetes-nmstate-operator.4.17.0-202210210157 Succeeded +kubernetes-nmstate-operator.4.18.0-202210210157 Succeeded ---- . Create an instance of the `nmstate` Operator: diff --git a/modules/logging-loki-storage-odf.adoc b/modules/logging-loki-storage-odf.adoc index dc88ed867cd4..3fe69f83bf88 100644 --- a/modules/logging-loki-storage-odf.adoc +++ b/modules/logging-loki-storage-odf.adoc @@ -10,7 +10,7 @@ * You installed the {loki-op}. * You installed the {oc-first}. * You deployed link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/[{rh-storage}]. -* You configured your {rh-storage} cluster link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.17/html/managing_and_allocating_storage_resources/adding-file-and-object-storage-to-an-existing-external-ocs-cluster[for object storage]. +* You configured your {rh-storage} cluster link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.18/html/managing_and_allocating_storage_resources/adding-file-and-object-storage-to-an-existing-external-ocs-cluster[for object storage]. .Procedure diff --git a/modules/manually-maintained-credentials-upgrade-extract.adoc b/modules/manually-maintained-credentials-upgrade-extract.adoc index 82b88b9194f9..2f5463c8cefd 100644 --- a/modules/manually-maintained-credentials-upgrade-extract.adoc +++ b/modules/manually-maintained-credentials-upgrade-extract.adoc @@ -32,7 +32,7 @@ The output of this command includes pull specs for the available updates similar Recommended updates: VERSION IMAGE -4.17.0 quay.io/openshift-release-dev/ocp-release@sha256:6a899c54dda6b844bb12a247e324a0f6cde367e880b73ba110c056df6d018032 +4.18.0 quay.io/openshift-release-dev/ocp-release@sha256:6a899c54dda6b844bb12a247e324a0f6cde367e880b73ba110c056df6d018032 ... ---- diff --git a/modules/manually-removing-cloud-creds.adoc b/modules/manually-removing-cloud-creds.adoc index 5d4b5c6e1ea2..3e0c2c359058 100644 --- a/modules/manually-removing-cloud-creds.adoc +++ b/modules/manually-removing-cloud-creds.adoc @@ -14,7 +14,7 @@ The CCO only requires the administrator-level credential during changes that req [NOTE] ==== -Before performing a minor version cluster update (for example, updating from {product-title} 4.16 to 4.17), you must reinstate the credential secret with the administrator-level credential. +Before performing a minor version cluster update (for example, updating from {product-title} {ocp-nminus1} to {product-version}), you must reinstate the credential secret with the administrator-level credential. If the credential is not present, the update might be blocked. ==== diff --git a/modules/mirror-registry-release-notes.adoc b/modules/mirror-registry-release-notes.adoc index 086da6993a02..acd0806200fd 100644 --- a/modules/mirror-registry-release-notes.adoc +++ b/modules/mirror-registry-release-notes.adoc @@ -94,7 +94,7 @@ New installations use SQLite by default. Before upgrading to version 2.0, see "U [id="mirror-registry-release-notes-1-3_{context}"] == Mirror registry for Red{nbsp}Hat OpenShift 1.3 release notes -To view the _mirror registry for Red{nbsp}Hat OpenShift_ 1.3 release notes, see link:https://docs.openshift.com/container-platform/4.17/installing/disconnected_install/installing-mirroring-creating-registry.html#mirror-registry-release-notes-1-3_installing-mirroring-creating-registry[Mirror registry for Red{nbsp}Hat OpenShift 1.3 release notes]. +To view the _mirror registry for Red{nbsp}Hat OpenShift_ 1.3 release notes, see link:https://docs.openshift.com/container-platform/4.18/installing/disconnected_install/installing-mirroring-creating-registry.html#mirror-registry-release-notes-1-3_installing-mirroring-creating-registry[Mirror registry for Red{nbsp}Hat OpenShift 1.3 release notes]. [id="mirror-registry-release-notes-1-2_{context}"] == Mirror registry for Red{nbsp}Hat OpenShift 1.2 release notes diff --git a/modules/oadp-gcp-wif-cloud-authentication.adoc b/modules/oadp-gcp-wif-cloud-authentication.adoc index 5b80e7f44df7..dcb747e496bc 100644 --- a/modules/oadp-gcp-wif-cloud-authentication.adoc +++ b/modules/oadp-gcp-wif-cloud-authentication.adoc @@ -25,7 +25,7 @@ If you do not use Google workload identity federation cloud authentication, cont .Prerequisites -* You have installed a cluster in manual mode with link:https://docs.openshift.com/container-platform/4.17/installing/installing_gcp/installing-gcp-customizations.html#installing-gcp-with-short-term-creds_installing-gcp-customizations[GCP Workload Identity configured]. +* You have installed a cluster in manual mode with link:https://docs.openshift.com/container-platform/4.18/installing/installing_gcp/installing-gcp-customizations.html#installing-gcp-with-short-term-creds_installing-gcp-customizations[GCP Workload Identity configured]. * You have access to the Cloud Credential Operator utility (`ccoctl`) and to the associated workload identity pool. .Procedure diff --git a/modules/oc-mirror-building-image-set-config-v2.adoc b/modules/oc-mirror-building-image-set-config-v2.adoc index 968b5c84f698..aa9fed35dfb9 100644 --- a/modules/oc-mirror-building-image-set-config-v2.adoc +++ b/modules/oc-mirror-building-image-set-config-v2.adoc @@ -26,12 +26,12 @@ apiVersion: mirror.openshift.io/v2alpha1 mirror: platform: channels: - - name: stable-4.17 <1> - minVersion: 4.17.2 - maxVersion: 4.17.2 + - name: stable-4.18 <1> + minVersion: 4.18.2 + maxVersion: 4.18.2 graph: true <2> operators: - - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.17 <3> + - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.18 <3> packages: <4> - name: aws-load-balancer-operator - name: 3scale-operator diff --git a/modules/oc-mirror-image-set-config-examples.adoc b/modules/oc-mirror-image-set-config-examples.adoc index 8c840b1b272d..0cbcc9e9f283 100644 --- a/modules/oc-mirror-image-set-config-examples.adoc +++ b/modules/oc-mirror-image-set-config-examples.adoc @@ -283,7 +283,7 @@ mirror: [id="oc-mirror-image-set-examples-mce-images-catalog-ocp_{context}"] == Use case: Including the multi-arch {product-title} images and catalog for {mce-short} -The following `ImageSetConfiguration` file includes {mce} and all {product-title} versions starting at a minimum version of `4.17.0` in the channel. +The following `ImageSetConfiguration` file includes {mce} and all {product-title} versions starting at a minimum version of `4.18.0` in the channel. .Example `ImageSetConfiguration` file [source,yaml,subs=attributes+] @@ -298,12 +298,12 @@ mirror: architectures: - "multi" channels: - - name: stable-4.17 - minVersion: 4.17.0 - maxVersion: 4.17.1 + - name: stable-4.18 + minVersion: 4.18.0 + maxVersion: 4.18.1 type: ocp operators: - - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.17 + - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.18 packages: - name: multicluster-engine ---- \ No newline at end of file diff --git a/modules/oc-mirror-imageset-config-params.adoc b/modules/oc-mirror-imageset-config-params.adoc index 4bf9c1505f19..c676981bd5a1 100644 --- a/modules/oc-mirror-imageset-config-params.adoc +++ b/modules/oc-mirror-imageset-config-params.adoc @@ -129,7 +129,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.17`. +|String. For example: `registry.redhat.io/redhat/redhat-operator-index:v4.18`. |`mirror.operators.full` |When `true`, downloads the full catalog, Operator package, or Operator channel. @@ -158,7 +158,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.17`. +|String. For example: `fast` or `stable-v4.18`. |`mirror.operators.packages.channels.maxVersion` |The highest version of the Operator mirror across all channels in which it exists. See the following note for further information. @@ -238,7 +238,7 @@ channels: |`mirror.platform.channels.name` |The name of the release channel. -|String. For example: `stable-4.17` +|String. For example: `stable-4.18` |`mirror.platform.channels.minVersion` |The minimum version of the referenced platform to be mirrored. @@ -246,7 +246,7 @@ channels: |`mirror.platform.channels.maxVersion` |The highest version of the referenced platform to be mirrored. -|String. For example: `4.17.1` +|String. For example: `4.18.1` |`mirror.platform.channels.shortestPath` |Toggles shortest path mirroring or full range mirroring. diff --git a/modules/odc-accessing-perspectives.adoc b/modules/odc-accessing-perspectives.adoc index 4475396dee9d..088cbe257268 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.17/web_console/adding-user-preferences.html[Adding User Preferences] for more information on changing perspectives. +See link:https://docs.openshift.com/container-platform/4.18/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 6872197f392e..3792561b26c3 100644 --- a/modules/olm-catalogsource-image-template.adoc +++ b/modules/olm-catalogsource-image-template.adoc @@ -14,11 +14,11 @@ endif::[] 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} {product-version}. -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.17 to 4.18, 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.18 to 4.18, 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.17 +registry.redhat.io/redhat/redhat-operator-index:v4.18 ---- to: diff --git a/modules/olmv1-adding-a-catalog.adoc b/modules/olmv1-adding-a-catalog.adoc index 50e1153a25f6..dad295773f00 100644 --- a/modules/olmv1-adding-a-catalog.adoc +++ b/modules/olmv1-adding-a-catalog.adoc @@ -90,7 +90,7 @@ Spec: Source: Image: Pull Secret: redhat-cred - Ref: registry.redhat.io/redhat/redhat-operator-index:v4.17 + Ref: registry.redhat.io/redhat/redhat-operator-index:v4.18 Type: image Status: <1> Conditions: @@ -105,7 +105,7 @@ Status: <1> Resolved Source: Image: Last Poll Attempt: 2024-06-10T17:35:10Z - Ref: registry.redhat.io/redhat/redhat-operator-index:v4.17 + Ref: registry.redhat.io/redhat/redhat-operator-index:v4.18 Resolved Ref: registry.redhat.io/redhat/redhat-operator-index@sha256:f2ccc079b5e490a50db532d1dc38fd659322594dcf3e653d650ead0e862029d9 <4> Type: image Events: diff --git a/modules/registry-configuring-registry-storage-rhodf-cephfs.adoc b/modules/registry-configuring-registry-storage-rhodf-cephfs.adoc index 82bf8891ae10..274b2407c95d 100644 --- a/modules/registry-configuring-registry-storage-rhodf-cephfs.adoc +++ b/modules/registry-configuring-registry-storage-rhodf-cephfs.adoc @@ -27,7 +27,7 @@ CephFS uses persistent volume claim (PVC) storage. It is not recommended to use * You have access to the cluster as a user with the `cluster-admin` role. * You have access to the {product-title} web console. * You installed the `oc` CLI. -* You installed the link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.17[{rh-storage} Operator] to provide object storage and CephFS file storage. +* You installed the link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.18[{rh-storage} Operator] to provide object storage and CephFS file storage. .Procedure diff --git a/modules/registry-configuring-registry-storage-rhodf-cephrgw.adoc b/modules/registry-configuring-registry-storage-rhodf-cephrgw.adoc index 72f72339a3ac..9410f70690c7 100644 --- a/modules/registry-configuring-registry-storage-rhodf-cephrgw.adoc +++ b/modules/registry-configuring-registry-storage-rhodf-cephrgw.adoc @@ -23,7 +23,7 @@ This document outlines the procedure to configure the image registry to use Ceph * You have access to the cluster as a user with the `cluster-admin` role. * You have access to the {product-title} web console. * You installed the `oc` CLI. -* You installed the link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.17[{rh-storage} Operator] to provide object storage and Ceph RGW object storage. +* You installed the link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.18[{rh-storage} Operator] to provide object storage and Ceph RGW object storage. .Procedure diff --git a/modules/registry-configuring-registry-storage-rhodf-nooba.adoc b/modules/registry-configuring-registry-storage-rhodf-nooba.adoc index ac233ff0b4a0..e6a0311b42b1 100644 --- a/modules/registry-configuring-registry-storage-rhodf-nooba.adoc +++ b/modules/registry-configuring-registry-storage-rhodf-nooba.adoc @@ -22,7 +22,7 @@ This document outlines the procedure to configure the image registry to use Noob * You have access to the cluster as a user with the `cluster-admin` role. * You have access to the {product-title} web console. * You installed the `oc` CLI. -* You installed the link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.17[{rh-storage} Operator] to provide object storage and Noobaa object storage. +* You installed the link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.18[{rh-storage} Operator] to provide object storage and Noobaa object storage. .Procedure diff --git a/modules/rosa-create-objects.adoc b/modules/rosa-create-objects.adoc index 4b8e8eaef1b7..c1bc2d88a094 100644 --- a/modules/rosa-create-objects.adoc +++ b/modules/rosa-create-objects.adoc @@ -314,7 +314,7 @@ Tags that are added by Red{nbsp}Hat are required for clusters to stay in complia ==== |--version string -|The version of ROSA that will be used to install the cluster or cluster resources. For `cluster` use an `X.Y.Z` format, for example, `4.17.0`. For `account-role` use an `X.Y` format, for example, `4.17`. +|The version of ROSA that will be used to install the cluster or cluster resources. For `cluster` use an `X.Y.Z` format, for example, `4.18.0`. For `account-role` use an `X.Y` format, for example, `4.18`. |--worker-iam-role string |The ARN of the IAM role that will be attached to compute instances. diff --git a/modules/rosa-deleting-account-wide-iam-roles-and-policies.adoc b/modules/rosa-deleting-account-wide-iam-roles-and-policies.adoc index f51e21902fe6..30442bb12ca8 100644 --- a/modules/rosa-deleting-account-wide-iam-roles-and-policies.adoc +++ b/modules/rosa-deleting-account-wide-iam-roles-and-policies.adoc @@ -75,9 +75,9 @@ ifdef::hcp[] ---- I: Fetching account roles ROLE NAME ROLE TYPE ROLE ARN OPENSHIFT VERSION AWS Managed -ManagedOpenShift-HCP-ROSA-Installer-Role Installer arn:aws:iam:::role/ManagedOpenShift-HCP-ROSA-Installer-Role 4.17 Yes -ManagedOpenShift-HCP-ROSA-Support-Role Support arn:aws:iam:::role/ManagedOpenShift-HCP-ROSA-Support-Role 4.17 Yes -ManagedOpenShift-HCP-ROSA-Worker-Role Worker arn:aws:iam:::role/ManagedOpenShift-HCP-ROSA-Worker-Role 4.17 Yes +ManagedOpenShift-HCP-ROSA-Installer-Role Installer arn:aws:iam:::role/ManagedOpenShift-HCP-ROSA-Installer-Role 4.18 Yes +ManagedOpenShift-HCP-ROSA-Support-Role Support arn:aws:iam:::role/ManagedOpenShift-HCP-ROSA-Support-Role 4.18 Yes +ManagedOpenShift-HCP-ROSA-Worker-Role Worker arn:aws:iam:::role/ManagedOpenShift-HCP-ROSA-Worker-Role 4.18 Yes ---- endif::hcp[] .. Delete the account-wide roles: diff --git a/modules/rosa-hcp-deleting-cluster.adoc b/modules/rosa-hcp-deleting-cluster.adoc index a703405accb2..f1908b1c4383 100644 --- a/modules/rosa-hcp-deleting-cluster.adoc +++ b/modules/rosa-hcp-deleting-cluster.adoc @@ -40,7 +40,7 @@ Display Name: test_cluster ID: <1> External ID: Control Plane: ROSA Service Hosted -OpenShift Version: 4.17.0 +OpenShift Version: 4.18.0 Channel Group: stable DNS: test_cluster.l3cn.p3.openshiftapps.com AWS Account: diff --git a/modules/rosa-hcp-sts-creating-a-cluster-external-auth-cluster-cli.adoc b/modules/rosa-hcp-sts-creating-a-cluster-external-auth-cluster-cli.adoc index 8fa3f5706a46..e8935e5e511f 100644 --- a/modules/rosa-hcp-sts-creating-a-cluster-external-auth-cluster-cli.adoc +++ b/modules/rosa-hcp-sts-creating-a-cluster-external-auth-cluster-cli.adoc @@ -56,7 +56,7 @@ Display Name: rosa-ext-test ID: External ID: Control Plane: ROSA Service Hosted -OpenShift Version: 4.17.0 +OpenShift Version: 4.18.0 Channel Group: stable DNS: AWS Account: diff --git a/modules/rosa-sts-account-wide-role-and-policy-commands.adoc b/modules/rosa-sts-account-wide-role-and-policy-commands.adoc index 7f6810508d71..93aeb46210d4 100644 --- a/modules/rosa-sts-account-wide-role-and-policy-commands.adoc +++ b/modules/rosa-sts-account-wide-role-and-policy-commands.adoc @@ -11,7 +11,7 @@ This section lists the `aws` CLI commands that the `rosa` command generates in t [id="rosa-sts-account-wide-role-and-policy-aws-cli-manual-mode_{context}"] == Using manual mode for account role creation -The manual role creation mode generates the `aws` commands for you to review and run. The following command starts that process, where `` refers to your version of {product-title} (ROSA), such as `4.17`. +The manual role creation mode generates the `aws` commands for you to review and run. The following command starts that process, where `` refers to your version of {product-title} (ROSA), such as `4.18`. [source,terminal] ---- diff --git a/modules/rosa-sts-account-wide-roles-and-policies.adoc b/modules/rosa-sts-account-wide-roles-and-policies.adoc index 012fcade4122..a629e1fec9ad 100644 --- a/modules/rosa-sts-account-wide-roles-and-policies.adoc +++ b/modules/rosa-sts-account-wide-roles-and-policies.adoc @@ -7,7 +7,7 @@ This section provides details about the account-wide IAM roles and policies that are required for ROSA deployments that use STS, including the Operator policies. It also includes the JSON files that define the policies. -The account-wide roles and policies are specific to an {product-title} minor release version, for example {product-title} 4.17, and are compatible with earlier versions. You can minimize the required STS resources by reusing the account-wide roles and policies for multiple clusters of the same minor version, regardless of their patch version. +The account-wide roles and policies are specific to an {product-title} minor release version, for example {product-title} {product-version}, and are compatible with earlier versions. You can minimize the required STS resources by reusing the account-wide roles and policies for multiple clusters of the same minor version, regardless of their patch version. [id="rosa-sts-account-wide-roles-and-policies-creation-methods_{context}"] == Methods of account-wide role creation @@ -52,7 +52,7 @@ The account number present in the `sts_installer_trust_policy.json` and `sts_sup ==== [source,json] ---- -include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.17/sts_installer_trust_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.18/sts_installer_trust_policy.json[] ---- ==== @@ -61,7 +61,7 @@ include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs ==== [source,json] ---- -include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.17/sts_installer_permission_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.18/sts_installer_permission_policy.json[] ---- ==== @@ -84,7 +84,7 @@ include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs ==== [source,json] ---- -include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.17/sts_instance_controlplane_trust_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.18/sts_instance_controlplane_trust_policy.json[] ---- ==== @@ -93,7 +93,7 @@ include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs ==== [source,json] ---- -include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.17/sts_instance_controlplane_permission_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.18/sts_instance_controlplane_permission_policy.json[] ---- ==== @@ -116,7 +116,7 @@ include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs ==== [source,json] ---- -include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.17/sts_instance_worker_trust_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.18/sts_instance_worker_trust_policy.json[] ---- ==== @@ -125,7 +125,7 @@ include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs ==== [source,json] ---- -include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.17/sts_instance_worker_permission_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.18/sts_instance_worker_permission_policy.json[] ---- ==== @@ -148,7 +148,7 @@ include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs ==== [source,json] ---- -include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.17/sts_support_trust_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.18/sts_support_trust_policy.json[] ---- ==== @@ -157,7 +157,7 @@ include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs ==== [source,json] ---- -include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.17/sts_support_permission_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.18/sts_support_permission_policy.json[] ---- ==== @@ -177,7 +177,7 @@ include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs ==== [source,json] ---- -include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.17/sts_ocm_trust_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.18/sts_ocm_trust_policy.json[] ---- ==== @@ -197,7 +197,7 @@ include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs ==== [source,json] ---- -include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.17/sts_installer_trust_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.18/sts_installer_trust_policy.json[] ---- ==== @@ -255,7 +255,7 @@ I: Attached policy 'arn:aws:iam::000000000000:policy/testrole-Worker-Role-Policy ==== [source,json] ---- -include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.17/openshift_ingress_operator_cloud_credentials_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.18/openshift_ingress_operator_cloud_credentials_policy.json[] ---- ==== @@ -275,7 +275,7 @@ include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs ==== [source,json] ---- -include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.17/openshift_cluster_csi_drivers_ebs_cloud_credentials_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.18/openshift_cluster_csi_drivers_ebs_cloud_credentials_policy.json[] ---- ==== @@ -295,7 +295,7 @@ include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs ==== [source,json] ---- -include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.17/openshift_machine_api_aws_cloud_credentials_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.18/openshift_machine_api_aws_cloud_credentials_policy.json[] ---- ==== @@ -315,7 +315,7 @@ include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs ==== [source,json] ---- -include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.17/openshift_cloud_credential_operator_cloud_credential_operator_iam_ro_creds_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.18/openshift_cloud_credential_operator_cloud_credential_operator_iam_ro_creds_policy.json[] ---- ==== @@ -335,6 +335,6 @@ include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs ==== [source,json] ---- -include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.17/openshift_image_registry_installer_cloud_credentials_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.18/openshift_image_registry_installer_cloud_credentials_policy.json[] ---- ==== diff --git a/modules/rosa-sts-aws-requirements-attaching-boundary-policy.adoc b/modules/rosa-sts-aws-requirements-attaching-boundary-policy.adoc index a7cd9609418e..96087f9e4879 100644 --- a/modules/rosa-sts-aws-requirements-attaching-boundary-policy.adoc +++ b/modules/rosa-sts-aws-requirements-attaching-boundary-policy.adoc @@ -42,7 +42,7 @@ This example procedure is applicable for an installer role and policy with the m ==== [source,json] ---- -include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.17/sts_installer_core_permission_boundary_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.18/sts_installer_core_permission_boundary_policy.json[] ---- ==== @@ -65,7 +65,7 @@ While the ROSA (`rosa`) CLI offers a permission boundary function, it applies to + [source,terminal] ---- -$ curl -o ./rosa-installer-core.json https://raw.githubusercontent.com/openshift/managed-cluster-config/master/resources/sts/4.17/sts_installer_core_permission_boundary_policy.json +$ curl -o ./rosa-installer-core.json https://raw.githubusercontent.com/openshift/managed-cluster-config/master/resources/sts/4.18/sts_installer_core_permission_boundary_policy.json ---- . Create the policy in AWS and gather its Amazon Resource Name (ARN) by entering the following command: @@ -128,7 +128,7 @@ For more examples of PL and VPC permission boundary policies see: ==== [source,json] ---- -include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.17/sts_installer_privatelink_permission_boundary_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.18/sts_installer_privatelink_permission_boundary_policy.json[] ---- ==== + @@ -137,6 +137,6 @@ include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs ==== [source,json] ---- -include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.17/sts_installer_vpc_permission_boundary_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.18/sts_installer_vpc_permission_boundary_policy.json[] ---- ==== 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 91d86eba40dd..188924b6e2a0 100644 --- a/modules/rosa-sts-creating-a-cluster-with-customizations-cli.adoc +++ b/modules/rosa-sts-creating-a-cluster-with-customizations-cli.adoc @@ -258,7 +258,7 @@ I: Using arn:aws:iam:::role/ManagedOpenShift-Support-Role for th ? Disable Workload monitoring (optional): No I: Creating cluster '' I: To create this cluster again in the future, you can run: - rosa create cluster --cluster-name --role-arn arn:aws:iam:::role/ManagedOpenShift-Installer-Role --support-role-arn arn:aws:iam:::role/ManagedOpenShift-Support-Role --master-iam-role arn:aws:iam:::role/ManagedOpenShift-ControlPlane-Role --worker-iam-role arn:aws:iam:::role/ManagedOpenShift-Worker-Role --operator-roles-prefix - --region us-east-1 --version 4.17.0 --additional-compute-security-group-ids sg-0e375ff0ec4a6cfa2 --additional-infra-security-group-ids sg-0e375ff0ec4a6cfa2 --additional-control-plane-security-group-ids sg-0e375ff0ec4a6cfa2 --replicas 2 --machine-cidr 10.0.0.0/16 --service-cidr 172.30.0.0/16 --pod-cidr 10.128.0.0/14 --host-prefix 23 <16> + rosa create cluster --cluster-name --role-arn arn:aws:iam:::role/ManagedOpenShift-Installer-Role --support-role-arn arn:aws:iam:::role/ManagedOpenShift-Support-Role --master-iam-role arn:aws:iam:::role/ManagedOpenShift-ControlPlane-Role --worker-iam-role arn:aws:iam:::role/ManagedOpenShift-Worker-Role --operator-roles-prefix - --region us-east-1 --version 4.18.0 --additional-compute-security-group-ids sg-0e375ff0ec4a6cfa2 --additional-infra-security-group-ids sg-0e375ff0ec4a6cfa2 --additional-control-plane-security-group-ids sg-0e375ff0ec4a6cfa2 --replicas 2 --machine-cidr 10.0.0.0/16 --service-cidr 172.30.0.0/16 --pod-cidr 10.128.0.0/14 --host-prefix 23 <16> I: To view a list of clusters and their status, run 'rosa list clusters' I: Cluster '' has been created. I: Once the cluster is installed you will need to add an Identity Provider before you can login into the cluster. See 'rosa create idp --help' for more information. @@ -267,7 +267,7 @@ I: Once the cluster is installed you will need to add an Identity Provider befor <1> Optional. When creating your cluster, you can customize the subdomain for your cluster on `*.openshiftapps.com` using the `--domain-prefix` flag. The value for this flag must be unique within your organization, cannot be longer than 15 characters, and cannot be changed after cluster creation. If the flag is not supplied, an autogenerated value is created that depends on the length of the cluster name. If the cluster name is fewer than or equal to 15 characters, that name is used for the domain prefix. If the cluster name is longer than 15 characters, the domain prefix is randomly generated to a 15 character string. <2> When creating your cluster, you can create a local administrator user (`cluster-admin`) for your cluster. This automatically configures an `htpasswd` identity provider for the `cluster-admin` user. <3> You can create a custom password for the `cluster-admin` user, or have the system generate a password. If you do not create a custom password, the generated password is displayed in the command line output. If you specify a custom password, the password must be at least 14 characters (ASCII-standard) without any whitespace. When defined, the password is hashed and transported securely. -<4> When creating the cluster, the listed `OpenShift version` options include the major, minor, and patch versions, for example `4.17.0`. +<4> When creating the cluster, the listed `OpenShift version` options include the major, minor, and patch versions, for example `4.18.0`. <5> Optional: Specify `optional` to configure all EC2 instances to use both v1 and v2 endpoints of EC2 Instance Metadata Service (IMDS). This is the default value. Specify `required` to configure all EC2 instances to use IMDSv2 only. + ifdef::openshift-rosa[] diff --git a/modules/sd-understanding-process-id-limits.adoc b/modules/sd-understanding-process-id-limits.adoc index 7ba8bfad5458..b896c38ccb68 100644 --- a/modules/sd-understanding-process-id-limits.adoc +++ b/modules/sd-understanding-process-id-limits.adoc @@ -14,7 +14,7 @@ The default value is 4,096 in {product-title} 4.11 and later. This value is cont * Maximum number of PIDs per node. + -The default value depends on link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.17/html-single/nodes/index#nodes-nodes-resources-configuring[node resources]. In {product-title}, this value is controlled by the link:https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#system-reserved[`--system-reserved`] parameter, which reserves PIDs on each node based on the total resources of the node. +The default value depends on link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.18/html-single/nodes/index#nodes-nodes-resources-configuring[node resources]. In {product-title}, this value is controlled by the link:https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#system-reserved[`--system-reserved`] parameter, which reserves PIDs on each node based on the total resources of the node. When a pod exceeds the allowed maximum number of PIDs per pod, the pod might stop functioning correctly and might be evicted from the node. See link:https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals-and-thresholds[the Kubernetes documentation for eviction signals and thresholds] for more information. diff --git a/modules/serverless-quarkus-template.adoc b/modules/serverless-quarkus-template.adoc index 7a263fdc169f..464fdf23d189 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.17 + 4.18 test diff --git a/modules/telco-core-load-balancer.adoc b/modules/telco-core-load-balancer.adoc index c085c0e9c82b..f35bf0e1a337 100644 --- a/modules/telco-core-load-balancer.adoc +++ b/modules/telco-core-load-balancer.adoc @@ -8,7 +8,7 @@ New in this release:: //CNF-11914 -* In {product-title} 4.17, `frr-k8s` is now the default and fully supported Border Gateway Protocol (BGP) backend. +* In {product-title} or later, `frr-k8s` is now the default and fully supported Border Gateway Protocol (BGP) backend. The deprecated `frr` BGP mode is still available. You should upgrade clusters to use the `frr-k8s` backend. diff --git a/modules/telco-core-rds-container.adoc b/modules/telco-core-rds-container.adoc index 81451665e335..070cebc36ce0 100644 --- a/modules/telco-core-rds-container.adoc +++ b/modules/telco-core-rds-container.adoc @@ -24,7 +24,7 @@ $ mkdir -p ./out + [source,terminal] ---- -$ podman run -it registry.redhat.io/openshift4/openshift-telco-core-rds-rhel9:v4.17 | base64 -d | tar xv -C out +$ podman run -it registry.redhat.io/openshift4/openshift-telco-core-rds-rhel9:v4.18 | base64 -d | tar xv -C out ---- .Verification diff --git a/modules/update-preparing-ack.adoc b/modules/update-preparing-ack.adoc index 26b558305c45..19223c1b1eca 100644 --- a/modules/update-preparing-ack.adoc +++ b/modules/update-preparing-ack.adoc @@ -6,7 +6,7 @@ [id="update-preparing-ack_{context}"] = Providing the administrator acknowledgment -After you have evaluated your cluster for any removed APIs and have migrated any removed APIs, you can acknowledge that your cluster is ready to upgrade from {product-title} 4.16 to 4.17. +After you have evaluated your cluster for any removed APIs and have migrated any removed APIs, you can acknowledge that your cluster is ready to upgrade from {product-title} {ocp-nminus1} to {product-version}. [WARNING] ==== @@ -19,9 +19,9 @@ Be aware that all responsibility falls on the administrator to ensure that all u .Procedure -* Run the following command to acknowledge that you have completed the evaluation and your cluster is ready for the Kubernetes API removals in {product-title} 4.17: +* Run the following command to acknowledge that you have completed the evaluation and your cluster is ready for the Kubernetes API removals in {product-title} {product-version}: + [source,terminal] ---- -$ oc -n openshift-config patch cm admin-acks --patch '{"data":{"ack-4.15-kube-1.29-api-removals-in-4.17":"true"}}' --type=merge +$ oc -n openshift-config patch cm admin-acks --patch '{"data":{"ack-4.15-kube-1.29-api-removals-in-4.18":"true"}}' --type=merge ---- diff --git a/modules/using-cluster-compare-telco-ref.adoc b/modules/using-cluster-compare-telco-ref.adoc index 8c82dcaa2545..7c90bad5138b 100644 --- a/modules/using-cluster-compare-telco-ref.adoc +++ b/modules/using-cluster-compare-telco-ref.adoc @@ -69,7 +69,7 @@ $ mkdir -p ./out + [source,terminal] ---- -$ podman run -it registry.redhat.io/openshift4/openshift-telco-core-rds-rhel9:v4.17 | base64 -d | tar xv -C out +$ podman run -it registry.redhat.io/openshift4/openshift-telco-core-rds-rhel9:v4.18 | base64 -d | tar xv -C out ---- + You can view the reference configuration in the `reference-crs-kube-compare/` directory. diff --git a/modules/verifying-cluster-install-oci-agent-based.adoc b/modules/verifying-cluster-install-oci-agent-based.adoc index 78d2059c02d6..88ae061b2005 100644 --- a/modules/verifying-cluster-install-oci-agent-based.adoc +++ b/modules/verifying-cluster-install-oci-agent-based.adoc @@ -63,8 +63,8 @@ $ oc get co [source,terminal] ---- NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE -authentication 4.17.0-0 True False False 6m18s -baremetal 4.17.0-0 True False False 2m42s -network 4.17.0-0 True True False 5m58s Progressing: … +authentication 4.18.0-0 True False False 6m18s +baremetal 4.18.0-0 True False False 2m42s +network 4.18.0-0 True True False 5m58s Progressing: … … ---- diff --git a/modules/virt-checking-storage-configuration.adoc b/modules/virt-checking-storage-configuration.adoc index de347104e53a..ffc646f939d4 100644 --- a/modules/virt-checking-storage-configuration.adoc +++ b/modules/virt-checking-storage-configuration.adoc @@ -167,11 +167,11 @@ data: status.failureReason: "" # <2> status.startTimestamp: "2023-07-31T13:14:38Z" # <3> status.completionTimestamp: "2023-07-31T13:19:41Z" # <4> - status.result.cnvVersion: 4.17.2 # <5> + status.result.cnvVersion: 4.18.2 # <5> status.result.defaultStorageClass: trident-nfs <6> status.result.goldenImagesNoDataSource: # <7> status.result.goldenImagesNotUpToDate: # <8> - status.result.ocpVersion: 4.17.0 # <9> + status.result.ocpVersion: 4.18.0 # <9> status.result.pvcBound: "true" # <10> status.result.storageProfileMissingVolumeSnapshotClass: # <11> status.result.storageProfilesWithEmptyClaimPropertySets: # <12> diff --git a/modules/virt-metro-dr-odf.adoc b/modules/virt-metro-dr-odf.adoc index 997e149992ec..2b85c78f23a2 100644 --- a/modules/virt-metro-dr-odf.adoc +++ b/modules/virt-metro-dr-odf.adoc @@ -6,7 +6,7 @@ [id="metro-dr-odf_{context}"] = Metro-DR for {rh-storage-first} -{VirtProductName} supports the link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.17/html-single/configuring_openshift_data_foundation_disaster_recovery_for_openshift_workloads/index#metro-dr-solution[Metro-DR solution for {rh-storage}], which provides two-way synchronous data replication between managed {VirtProductName} clusters installed on primary and secondary sites. +{VirtProductName} supports the link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.18/html-single/configuring_openshift_data_foundation_disaster_recovery_for_openshift_workloads/index#metro-dr-solution[Metro-DR solution for {rh-storage}], which provides two-way synchronous data replication between managed {VirtProductName} clusters installed on primary and secondary sites. .Metro-DR differences * This synchronous solution is only available to metropolitan distance data centers with a network round-trip latency of 10 milliseconds or less. diff --git a/modules/virt-regional-dr-odf.adoc b/modules/virt-regional-dr-odf.adoc index 928899ddcd69..c608247f4430 100644 --- a/modules/virt-regional-dr-odf.adoc +++ b/modules/virt-regional-dr-odf.adoc @@ -6,7 +6,7 @@ [id="regional-dr-odf_{context}"] = Regional-DR for {rh-storage-first} -{VirtProductName} supports the link:https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.17/html-single/configuring_openshift_data_foundation_disaster_recovery_for_openshift_workloads/index#rdr-solution[Regional-DR solution for {rh-storage}], which provides asynchronous data replication at regular intervals between managed {VirtProductName} clusters installed on primary and secondary sites. +{VirtProductName} supports the link:https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.18/html-single/configuring_openshift_data_foundation_disaster_recovery_for_openshift_workloads/index#rdr-solution[Regional-DR solution for {rh-storage}], which provides asynchronous data replication at regular intervals between managed {VirtProductName} clusters installed on primary and secondary sites. .Regional-DR differences * Regional-DR supports higher network latency between the primary and secondary sites. diff --git a/modules/virt-using-wasp-agent-to-configure-higher-vm-workload-density.adoc b/modules/virt-using-wasp-agent-to-configure-higher-vm-workload-density.adoc index 1d422e61cbea..160a7dde02f6 100644 --- a/modules/virt-using-wasp-agent-to-configure-higher-vm-workload-density.adoc +++ b/modules/virt-using-wasp-agent-to-configure-higher-vm-workload-density.adoc @@ -188,7 +188,7 @@ spec: fieldRef: fieldPath: spec.nodeName image: >- - quay.io/openshift-virtualization/wasp-agent:v4.17 <1> + quay.io/openshift-virtualization/wasp-agent:v4.18 <1> imagePullPolicy: Always name: wasp-agent resources: diff --git a/modules/ztp-image-based-upgrade-procedure-rollback.adoc b/modules/ztp-image-based-upgrade-procedure-rollback.adoc index e0ed6b945d51..37877fd10dbd 100644 --- a/modules/ztp-image-based-upgrade-procedure-rollback.adoc +++ b/modules/ztp-image-based-upgrade-procedure-rollback.adoc @@ -34,8 +34,8 @@ spec: - spoke4 ibuSpec: seedImageRef: - image: quay.io/seed/image:4.17.0-rc.1 - version: 4.17.0-rc.1 + image: quay.io/seed/image:4.18.0-rc.1 + version: 4.18.0-rc.1 pullSecretRef: name: "" extraManifests: diff --git a/osd_planning/gcp-ccs.adoc b/osd_planning/gcp-ccs.adoc index 968be0ed5dd4..195baa506bff 100644 --- a/osd_planning/gcp-ccs.adoc +++ b/osd_planning/gcp-ccs.adoc @@ -26,4 +26,4 @@ include::modules/osd-gcp-psc-firewall-prerequisites.adoc[leveloffset=+1] * For more information about creating an {product-title} cluster with the Workload Identity Federation (WIF) authentication type, see xref:../osd_gcp_clusters/creating-a-gcp-cluster-with-workload-identity-federation.adoc#create-wif-cluster-cli_osd-creating-a-cluster-on-gcp-with-workload-identity-federation[Creating a WIF configuration]. -* For more information about the specific roles and permissions that are specific to clusters created when using the Workload Identity Federation (WIF) authentication type, see link:https://github.com/openshift/managed-cluster-config/blob/master/resources/wif/4.17/vanilla.yaml[managed-cluster-config]. +* For more information about the specific roles and permissions that are specific to clusters created when using the Workload Identity Federation (WIF) authentication type, see link:https://github.com/openshift/managed-cluster-config/blob/master/resources/wif/4.18/vanilla.yaml[managed-cluster-config]. diff --git a/registry/configuring_registry_storage/configuring-registry-storage-baremetal.adoc b/registry/configuring_registry_storage/configuring-registry-storage-baremetal.adoc index 0089961465d0..4744b2118eeb 100644 --- a/registry/configuring_registry_storage/configuring-registry-storage-baremetal.adoc +++ b/registry/configuring_registry_storage/configuring-registry-storage-baremetal.adoc @@ -29,4 +29,4 @@ include::modules/registry-configuring-registry-storage-rhodf-cephfs.adoc[levelof == Additional resources * xref:../../scalability_and_performance/optimization/optimizing-storage.adoc#optimizing-storage[Recommended configurable storage technology] -* link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.17/html-single/managing_and_allocating_storage_resources/index#configuring-image-registry-to-use-openshift-data-foundation_rhodf[Configuring Image Registry to use OpenShift Data Foundation] +* link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.18/html-single/managing_and_allocating_storage_resources/index#configuring-image-registry-to-use-openshift-data-foundation_rhodf[Configuring Image Registry to use OpenShift Data Foundation] diff --git a/registry/configuring_registry_storage/configuring-registry-storage-nutanix.adoc b/registry/configuring_registry_storage/configuring-registry-storage-nutanix.adoc index 489ff773b86d..d1cd042c676f 100644 --- a/registry/configuring_registry_storage/configuring-registry-storage-nutanix.adoc +++ b/registry/configuring_registry_storage/configuring-registry-storage-nutanix.adoc @@ -30,4 +30,4 @@ include::modules/registry-configuring-registry-storage-rhodf-cephfs.adoc[levelof == Additional resources * xref:../../scalability_and_performance/optimization/optimizing-storage.adoc#optimizing-storage[Recommended configurable storage technology] -* link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.17/html-single/managing_and_allocating_storage_resources/index#configuring-image-registry-to-use-openshift-data-foundation_rhodf[Configuring Image Registry to use OpenShift Data Foundation] +* link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.18/html-single/managing_and_allocating_storage_resources/index#configuring-image-registry-to-use-openshift-data-foundation_rhodf[Configuring Image Registry to use OpenShift Data Foundation] diff --git a/registry/configuring_registry_storage/configuring-registry-storage-rhodf.adoc b/registry/configuring_registry_storage/configuring-registry-storage-rhodf.adoc index 2c41bc9b66da..29f2c9b0b3ce 100644 --- a/registry/configuring_registry_storage/configuring-registry-storage-rhodf.adoc +++ b/registry/configuring_registry_storage/configuring-registry-storage-rhodf.adoc @@ -18,5 +18,5 @@ include::modules/registry-configuring-registry-storage-rhodf-cephfs.adoc[levelof [role="_additional-resources"] == Additional resources -* link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.17/html-single/managing_and_allocating_storage_resources/index#configuring-image-registry-to-use-openshift-data-foundation_rhodf[Configuring Image Registry to use OpenShift Data Foundation] +* link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.18/html-single/managing_and_allocating_storage_resources/index#configuring-image-registry-to-use-openshift-data-foundation_rhodf[Configuring Image Registry to use OpenShift Data Foundation] * link:https://access.redhat.com/solutions/6719951[Performance tuning guide for Multicloud Object Gateway (NooBaa)] diff --git a/registry/configuring_registry_storage/configuring-registry-storage-vsphere.adoc b/registry/configuring_registry_storage/configuring-registry-storage-vsphere.adoc index 57c33fa3086a..0b483f85ae0d 100644 --- a/registry/configuring_registry_storage/configuring-registry-storage-vsphere.adoc +++ b/registry/configuring_registry_storage/configuring-registry-storage-vsphere.adoc @@ -31,4 +31,4 @@ include::modules/registry-configuring-registry-storage-rhodf-cephfs.adoc[levelof == Additional resources * xref:../../scalability_and_performance/optimization/optimizing-storage.adoc#optimizing-storage[Recommended configurable storage technology] -* link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.17/html-single/managing_and_allocating_storage_resources/index#configuring-image-registry-to-use-openshift-data-foundation_rhodf[Configuring Image Registry to use OpenShift Data Foundation] +* link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.18/html-single/managing_and_allocating_storage_resources/index#configuring-image-registry-to-use-openshift-data-foundation_rhodf[Configuring Image Registry to use OpenShift Data Foundation] diff --git a/snippets/ibu-ImageBasedGroupUpgrade.adoc b/snippets/ibu-ImageBasedGroupUpgrade.adoc index 57325cad6d57..faddde60ff2a 100644 --- a/snippets/ibu-ImageBasedGroupUpgrade.adoc +++ b/snippets/ibu-ImageBasedGroupUpgrade.adoc @@ -16,8 +16,8 @@ spec: - spoke6 ibuSpec: seedImageRef: # <2> - image: quay.io/seed/image:4.17.0-rc.1 - version: 4.17.0-rc.1 + image: quay.io/seed/image:4.18.0-rc.1 + version: 4.18.0-rc.1 pullSecretRef: name: "" extraManifests: # <3> 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 ed1458c8dbd7..7fe747cf2701 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 link:https://github.com/openshift/aws-efs-csi- {product-title} is capable of provisioning persistent volumes (PVs) using the link:https://github.com/openshift/aws-efs-csi-driver[AWS EFS CSI driver]. -Familiarity with link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.17/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.17/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.18/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.18/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.17/html-single/storage/index#persistent-storage-csi[Configuring CSI volumes] +* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.18/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 3a412c675521..7d063d48947a 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.17/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.17/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.18/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.18/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.17/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.18/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.17/html-single/storage/index#persistent-storage-csi[Configuring CSI volumes] +* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.18/html-single/storage/index#persistent-storage-csi[Configuring CSI volumes] diff --git a/support/approved-access.adoc b/support/approved-access.adoc index 064819defd71..d476f2f8cd5a 100644 --- a/support/approved-access.adoc +++ b/support/approved-access.adoc @@ -9,7 +9,7 @@ endif::[] toc::[] -Red{nbsp}Hat Site Reliability Engineering (SRE) typically does not require elevated access to systems as part of normal operations to manage and support {product-title} clusters. Elevated access gives SRE the access levels of a cluster-admin role. See link:https://docs.openshift.com/container-platform/4.17/authentication/using-rbac.html#default-roles_using-rbac[cluster roles] for more information. +Red{nbsp}Hat Site Reliability Engineering (SRE) typically does not require elevated access to systems as part of normal operations to manage and support {product-title} clusters. Elevated access gives SRE the access levels of a cluster-admin role. See link:https://docs.openshift.com/container-platform/4.18/authentication/using-rbac.html#default-roles_using-rbac[cluster roles] for more information. In the unlikely event that SRE needs elevated access to systems, you can use the _Approved Access_ interface to review and _approve_ or _deny_ access to these systems. diff --git a/virt/backup_restore/virt-disaster-recovery.adoc b/virt/backup_restore/virt-disaster-recovery.adoc index 9152f0befddf..bc0f26e536ba 100644 --- a/virt/backup_restore/virt-disaster-recovery.adoc +++ b/virt/backup_restore/virt-disaster-recovery.adoc @@ -23,6 +23,6 @@ include::modules/virt-regional-dr-odf.adoc[leveloffset=+2] [role="_additional-resources"] [id="additional-resources_{context}"] == Additional resources -* link:https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.17/html/configuring_openshift_data_foundation_disaster_recovery_for_openshift_workloads/index[Configuring {rh-storage} Disaster Recovery for OpenShift Workloads] +* link:https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.18/html/configuring_openshift_data_foundation_disaster_recovery_for_openshift_workloads/index[Configuring {rh-storage} Disaster Recovery for OpenShift Workloads] * link:https://access.redhat.com/articles/7053115[Use {rh-storage} Disaster Recovery to Protect Virtual Machines] in the Red{nbsp}Hat Knowledgebase * link:https://docs.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.10[Red{nbsp}Hat Advanced Cluster Management for Kubernetes 2.10] \ No newline at end of file diff --git a/virt/support/virt-collecting-virt-data.adoc b/virt/support/virt-collecting-virt-data.adoc index 5ff7c8d17a71..89fcaf8bd117 100644 --- a/virt/support/virt-collecting-virt-data.adoc +++ b/virt/support/virt-collecting-virt-data.adoc @@ -39,7 +39,7 @@ Collecting data about your environment minimizes the time required to analyze an // must-gather not supported for ROSA/OSD, per Dustin Row ifndef::openshift-rosa,openshift-dedicated[] . 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.17/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.18/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:../../observability/monitoring/managing-metrics.adoc#querying-metrics-for-all-projects-as-an-administrator_managing-metrics[Collect Prometheus metrics for the cluster]. endif::openshift-rosa,openshift-dedicated[]