From 722462e107ca6706a9709398862a13ebf883e0c4 Mon Sep 17 00:00:00 2001 From: cbippley Date: Thu, 29 May 2025 16:46:35 -0400 Subject: [PATCH] OSDOCS-13550 hardcoded 4.19 version number bump --- ...an-aws-iam-role-for-a-service-account.adoc | 2 +- ...d-experts-osd-update-component-routes.adoc | 2 +- modules/about-developer-perspective.adoc | 2 +- modules/agent-installer-architectures.adoc | 2 +- ...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 +- ...hcp-ibm-z-adding-reg-ca-hostedcluster.adoc | 2 +- modules/hcp-non-bm-hc-mirror.adoc | 2 +- modules/hcp-non-bm-hc.adoc | 2 +- modules/hcp-support-matrix.adoc | 4 +- modules/hibernating-cluster-hibernate.adoc | 16 ++++---- modules/hibernating-cluster-resume.adoc | 16 ++++---- ...hosted-control-planes-version-support.adoc | 2 +- modules/ibi-create-iso-for-bmh.adoc | 12 +++--- .../ibi-extra-partition-ibi-install-iso.adoc | 10 ++--- .../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 +- ...allation-aws-arm-tested-machine-types.adoc | 2 +- ...installation-aws-tested-machine-types.adoc | 2 +- ...lation-azure-arm-tested-machine-types.adoc | 2 +- ...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 +- ...allation-gcp-tested-machine-types-arm.adoc | 2 +- ...installation-gcp-tested-machine-types.adoc | 2 +- ...lation-ibm-cloud-tested-machine-types.adoc | 2 +- modules/installation-special-config-kmod.adoc | 4 +- .../installation-special-config-rtkernel.adoc | 2 +- .../installation-user-infra-machines-iso.adoc | 10 ++--- .../installation-user-infra-machines-pxe.adoc | 24 +++++------ ...ling-a-cluster-with-multiarch-support.adoc | 4 +- modules/k8s-nmstate-uninstall-operator.adoc | 7 ++-- modules/logging-loki-storage-odf.adoc | 2 +- ...aintained-credentials-upgrade-extract.adoc | 2 +- modules/migration-configuring-mcg.adoc | 2 +- modules/mirror-registry-release-notes.adoc | 4 +- modules/multi-architecture-scheduling.adoc | 2 +- modules/nodes-nodes-viewing-listing.adoc | 6 +-- modules/nw-dpu-operator-uninstall.adoc | 4 +- .../oadp-gcp-wif-cloud-authentication.adoc | 2 +- ...c-mirror-building-image-set-config-v2.adoc | 8 ++-- .../oc-mirror-image-set-config-examples.adoc | 12 +++--- modules/oc-mirror-imageset-config-params.adoc | 8 ++-- modules/odc-accessing-perspectives.adoc | 2 +- modules/osd-lifecycle-policy.adoc | 5 +-- ...iguring-registry-storage-rhodf-cephfs.adoc | 3 +- ...guring-registry-storage-rhodf-cephrgw.adoc | 4 +- ...figuring-registry-storage-rhodf-nooba.adoc | 3 +- modules/rosa-create-objects.adoc | 10 ++--- ...g-account-wide-iam-roles-and-policies.adoc | 40 +++++++++---------- modules/rosa-hcp-deleting-cluster.adoc | 6 +-- ...g-a-cluster-external-auth-cluster-cli.adoc | 4 +- ...a-sts-account-wide-roles-and-policies.adoc | 40 +++++++++---------- ...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 +- ...fying-cluster-install-oci-agent-based.adoc | 6 +-- .../virt-checking-storage-configuration.adoc | 4 +- modules/virt-metro-dr-odf.adoc | 8 ++-- modules/virt-regional-dr-odf.adoc | 2 +- ...-configure-higher-vm-workload-density.adoc | 4 +- ...mage-based-upgrade-procedure-rollback.adoc | 6 +-- modules/ztp-sno-accelerated-ztp.adoc | 26 ++++++------ .../ztp-sno-siteconfig-config-reference.adoc | 2 +- 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 +- .../telco-hub-rds.adoc | 4 +- snippets/ibu-ImageBasedGroupUpgrade.adoc | 4 +- .../osd-persistent-storage-aws-efs-csi.adoc | 5 +-- .../rosa-persistent-storage-aws-efs-csi.adoc | 7 ++-- support/approved-access.adoc | 2 +- .../virt-disaster-recovery.adoc | 2 +- .../virt-creating-vms-by-cloning-pvcs.adoc | 4 +- virt/support/virt-collecting-virt-data.adoc | 2 +- 99 files changed, 240 insertions(+), 250 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 3b6f55d07d..d1405fb494 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,openshift-rosa-hcp[] -* 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. +* For general information about webhook admission plugins for OpenShift, see link:https://docs.openshift.com/container-platform/latest/architecture/admission-plug-ins.html#admission-webhooks-about_admission-plug-ins[Webhook admission plugins] in the {product-title} documentation. endif::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[] diff --git a/cloud_experts_osd_tutorials/cloud-experts-osd-update-component-routes.adoc b/cloud_experts_osd_tutorials/cloud-experts-osd-update-component-routes.adoc index a79e4f2d9f..c2653c9c63 100644 --- a/cloud_experts_osd_tutorials/cloud-experts-osd-update-component-routes.adoc +++ b/cloud_experts_osd_tutorials/cloud-experts-osd-update-component-routes.adoc @@ -12,7 +12,7 @@ toc::[] //Article text This guide demonstrates how to modify the hostname and TLS certificate of the Web console, OAuth server, and Downloads component routes in {product-title} on {GCP} version 4.14 and above.{fn-supported-versions} -The changes that we make to the component routes{fn-term-component-routes} in this guide are described in greater detail in the link:https://docs.openshift.com/container-platform/latest/authentication/configuring-internal-oauth.html#customizing-the-oauth-server-url_configuring-internal-oauth[Customing the internal OAuth server URL], link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/web_console/customizing-web-console#customizing-the-console-route_customizing-web-console[Customing the console route], and link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/web_console/customizing-web-console#customizing-the-download-route_customizing-web-console[Customing the download route] OpenShift Container Platform documentation. +The changes that we make to the component routes{fn-term-component-routes} in this guide are described in greater detail in the link:https://docs.openshift.com/container-platform/latest/authentication/configuring-internal-oauth.html#customizing-the-oauth-server-url_configuring-internal-oauth[Customing the internal OAuth server URL], link:https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html/web_console/customizing-web-console#customizing-the-console-route_customizing-web-console[Customing the console route], and link:https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html/web_console/customizing-web-console#customizing-the-download-route_customizing-web-console[Customing the download route] {product-title} documentation. [id="prerequisites_{context}"] == Prerequisites diff --git a/modules/about-developer-perspective.adoc b/modules/about-developer-perspective.adoc index 7449c01916..a7e457e5c6 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.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. +See link:https://docs.openshift.com/container-platform/latest/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/agent-installer-architectures.adoc b/modules/agent-installer-architectures.adoc index 5dc2676ac6..65be004525 100644 --- a/modules/agent-installer-architectures.adoc +++ b/modules/agent-installer-architectures.adoc @@ -27,7 +27,7 @@ $ ./openshift-install version .Example output [source,terminal] ---- -./openshift-install 4.18.0 +./openshift-install 4.19.0 built from commit abc123def456 release image quay.io/openshift-release-dev/ocp-release@sha256:123abc456def789ghi012jkl345mno678pqr901stu234vwx567yz0 release architecture amd64 diff --git a/modules/creating-config-files-cluster-install-oci.adoc b/modules/creating-config-files-cluster-install-oci.adoc index 9b00372812..1280d68782 100644 --- a/modules/creating-config-files-cluster-install-oci.adoc +++ b/modules/creating-config-files-cluster-install-oci.adoc @@ -60,9 +60,9 @@ $ ./openshift-install version .Example output for a shared registry binary [source,terminal,subs="quotes"] ---- -./openshift-install 4.18.0 +./openshift-install 4.19.0 built from commit ae7977b7d1ca908674a0d45c5c243c766fa4b2ca -release image registry.ci.openshift.org/origin/release:4.18ocp-release@sha256:0da6316466d60a3a4535d5fed3589feb0391989982fba59d47d4c729912d6363 +release image registry.ci.openshift.org/origin/release:4.19ocp-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 fb7185bad3..bd5a51049c 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.18.0-multi`. +<8> Specify the supported {product-title} version that you want to use, for example, `4.19.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 0248b7c692..89f0e609fb 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.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 +<9> Specify the supported {product-title} version that you want to use, for example, `4.19.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 a154f0401d..bff187da6d 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.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_. +<10> Specify the supported {product-title} version that you want to use, for example, `4.19.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 53550963e6..73e9597861 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.18.0-multi`. +Replace `<4.x.y>` with the supported {product-title} version that you want to use, for example, `4.19.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 f5fdb29055..974aa529ef 100644 --- a/modules/hcp-create-hc-arm64-aws.adoc +++ b/modules/hcp-create-hc-arm64-aws.adoc @@ -37,5 +37,5 @@ $ 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.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". +<7> Specify the supported {product-title} version that you want to use, for example, `4.19.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`. \ No newline at end of file diff --git a/modules/hcp-ibm-z-adding-reg-ca-hostedcluster.adoc b/modules/hcp-ibm-z-adding-reg-ca-hostedcluster.adoc index 1fe8647721..0cd3a96b83 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.18.0-multi`. +<7> Replace with the supported {product-title} version that you want to use, for example, `4.19.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 e57f990c4c..300ce3e867 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.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_. +<9> Specify the supported {product-title} version that you want to use, for example, `4.19.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 b91bd741f8..2d97f5be93 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.18.0-multi`. +<10> Specify the supported {product-title} version that you want to use, for example, `4.19.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/hcp-support-matrix.adoc b/modules/hcp-support-matrix.adoc index 7094bce893..96f94dafd3 100644 --- a/modules/hcp-support-matrix.adoc +++ b/modules/hcp-support-matrix.adoc @@ -56,7 +56,7 @@ The following table maps {mce-short} versions to the hosted cluster versions tha [NOTE] ==== -Although the HyperShift Operator supports the hosted cluster versions in the following table, {mce-short} supports only as far back as 2 versions earlier than the current version. For example, if the current hosted cluster version is 4.18, {mce-short} supports as far back as version 4.16. If you want to use a hosted cluster version that is earlier than one of the versions that {mce-short} supports, you can detach your hosted clusters from {mce-short} to be unmanaged, or you can use an earlier version of {mce-short}. For more information, see link:https://access.redhat.com/articles/7099674[The multicluster engine for Kubernetes operator 2.8 Support Matrix]. +Although the HyperShift Operator supports the hosted cluster versions in the following table, {mce-short} supports only as far back as 2 versions earlier than the current version. For example, if the current hosted cluster version is 4.19, {mce-short} supports as far back as version 4.17. If you want to use a hosted cluster version that is earlier than one of the versions that {mce-short} supports, you can detach your hosted clusters from {mce-short} to be unmanaged, or you can use an earlier version of {mce-short}. For more information, see link:https://access.redhat.com/articles/7099674[The multicluster engine for Kubernetes operator 2.8 Support Matrix]. ==== .Hosted cluster versions that can be created by {mce-short} versions @@ -277,7 +277,7 @@ When you update to another version of the {mce-short}, your hosted cluster can c [NOTE] ==== -Although the HyperShift Operator supports the hosted cluster versions in the following table, {mce-short} supports only as far back as 2 versions earlier than the current version. For example, if the current hosted cluster version is 4.18, {mce-short} supports as far back as version 4.16. If you want to use a hosted cluster version that is earlier than one of the versions that {mce-short} supports, you can detach your hosted clusters from {mce-short} to be unmanaged, or you can use an earlier version of {mce-short}. For more information, see link:https://access.redhat.com/articles/7099674[The multicluster engine for Kubernetes operator 2.8 Support Matrix]. +Although the HyperShift Operator supports the hosted cluster versions in the following table, {mce-short} supports only as far back as 2 versions earlier than the current version. For example, if the current hosted cluster version is 4.19, {mce-short} supports as far back as version 4.17. If you want to use a hosted cluster version that is earlier than one of the versions that {mce-short} supports, you can detach your hosted clusters from {mce-short} to be unmanaged, or you can use an earlier version of {mce-short}. For more information, see link:https://access.redhat.com/articles/7099674[The multicluster engine for Kubernetes operator 2.8 Support Matrix]. ==== .Updated {mce-short} version support for hosted clusters diff --git a/modules/hibernating-cluster-hibernate.adoc b/modules/hibernating-cluster-hibernate.adoc index 926dd86039..ef0805eaad 100644 --- a/modules/hibernating-cluster-hibernate.adoc +++ b/modules/hibernating-cluster-hibernate.adoc @@ -57,14 +57,14 @@ $ oc get clusteroperators [source,terminal] ---- NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE -authentication 4.18.0-0 True False False 51m -baremetal 4.18.0-0 True False False 72m -cloud-controller-manager 4.18.0-0 True False False 75m -cloud-credential 4.18.0-0 True False False 77m -cluster-api 4.18.0-0 True False False 42m -cluster-autoscaler 4.18.0-0 True False False 72m -config-operator 4.18.0-0 True False False 72m -console 4.18.0-0 True False False 55m +authentication 4.19.0-0 True False False 51m +baremetal 4.19.0-0 True False False 72m +cloud-controller-manager 4.19.0-0 True False False 75m +cloud-credential 4.19.0-0 True False False 77m +cluster-api 4.19.0-0 True False False 42m +cluster-autoscaler 4.19.0-0 True False False 72m +config-operator 4.19.0-0 True False False 72m +console 4.19.0-0 True False False 55m ... ---- + diff --git a/modules/hibernating-cluster-resume.adoc b/modules/hibernating-cluster-resume.adoc index fd8ee458f6..69d7fd24f4 100644 --- a/modules/hibernating-cluster-resume.adoc +++ b/modules/hibernating-cluster-resume.adoc @@ -104,14 +104,14 @@ $ oc get clusteroperators [source,terminal] ---- NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE -authentication 4.18.0-0 True False False 51m -baremetal 4.18.0-0 True False False 72m -cloud-controller-manager 4.18.0-0 True False False 75m -cloud-credential 4.18.0-0 True False False 77m -cluster-api 4.18.0-0 True False False 42m -cluster-autoscaler 4.18.0-0 True False False 72m -config-operator 4.18.0-0 True False False 72m -console 4.18.0-0 True False False 55m +authentication 4.19.0-0 True False False 51m +baremetal 4.19.0-0 True False False 72m +cloud-controller-manager 4.19.0-0 True False False 75m +cloud-credential 4.19.0-0 True False False 77m +cluster-api 4.19.0-0 True False False 42m +cluster-autoscaler 4.19.0-0 True False False 72m +config-operator 4.19.0-0 True False False 72m +console 4.19.0-0 True False False 55m ... ---- + diff --git a/modules/hosted-control-planes-version-support.adoc b/modules/hosted-control-planes-version-support.adoc index 85dae5aba3..c1ac9a5bc9 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.18"]}' + supported-versions: '{"versions":["4.19"]}' kind: ConfigMap metadata: labels: diff --git a/modules/ibi-create-iso-for-bmh.adoc b/modules/ibi-create-iso-for-bmh.adoc index fde75f19d9..de379821c2 100644 --- a/modules/ibi-create-iso-for-bmh.adoc +++ b/modules/ibi-create-iso-for-bmh.adoc @@ -1,12 +1,12 @@ // Module included in the following assemblies: // -// * edge_computing/ibi-image-based-install.adoc +// * edge_computing/ibi-image-based-install.adoc :_mod-docs-content-type: PROCEDURE [id="ibi-create-iso-for-bmh_{context}"] = Creating a live installation ISO for a {sno} image-based installation -You can embed your {sno} seed image URL, and other installation artifacts, in a live installation ISO by using the `openshift-install` program. +You can embed your {sno} seed image URL, and other installation artifacts, in a live installation ISO by using the `openshift-install` program. [NOTE] ==== @@ -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.18.0 -seedVersion: 4.18.0 +seedImage: quay.io/openshift-kni/seed-image:4.19.0 +seedVersion: 4.19.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.18.0" +seedVersion: "4.19.0" extraPartitionStart: "-240G" installationDisk: /dev/disk/by-id/wwn-0x62c... sshKey: 'ssh-ed25519 AAAA...' @@ -123,7 +123,7 @@ networkConfig: ---- .. Create the live installation ISO by running the following command: -+ ++ [source,terminal] ---- $ openshift-install image-based create image --dir ibi-iso-workdir diff --git a/modules/ibi-extra-partition-ibi-install-iso.adoc b/modules/ibi-extra-partition-ibi-install-iso.adoc index 2a32591c8c..22deecade2 100644 --- a/modules/ibi-extra-partition-ibi-install-iso.adoc +++ b/modules/ibi-extra-partition-ibi-install-iso.adoc @@ -6,9 +6,9 @@ [id="ibi-extra-partition-ibi-install-iso_{context}"] = Configuring additional partitions on the target host -The installation ISO creates a partition for the `/var/lib/containers` directory as part of the image-based installation process. +The installation ISO creates a partition for the `/var/lib/containers` directory as part of the image-based installation process. -You can create additional partitions by using the `coreosInstallerArgs` specification. For example, in hard disks with adequate storage, you might need an additional partition for storage options, such as {lvms-first}. +You can create additional partitions by using the `coreosInstallerArgs` specification. For example, in hard disks with adequate storage, you might need an additional partition for storage options, such as {lvms-first}. [NOTE] ==== @@ -27,18 +27,18 @@ kind: ImageBasedInstallationConfig metadata: name: example-extra-partition seedImage: quay.io/repo-id/seed:latest -seedVersion: "4.18.0" +seedVersion: "4.19.0" installationDisk: /dev/sda pullSecret: '{"auths": ...}' # ... skipDiskCleanup: true <1> -coreosInstallerArgs: +coreosInstallerArgs: - "--save-partindex" <2> - "6" <3> ignitionConfigOverride: | { "ignition": { - "version": "3.2.0" + "version": "3.2.0" }, "storage": { "disks": [ diff --git a/modules/insights-operator-one-time-gather.adoc b/modules/insights-operator-one-time-gather.adoc index 810bcc8602..98beec0d5d 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.18/docs/gather-job.yaml[] +include::https://raw.githubusercontent.com/openshift/insights-operator/release-4.19/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 db9f76bab3..6bc87abfb9 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.18/upi/azure/04_bootstrap.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/upi/azure/04_bootstrap.json[] endif::ash[] ifdef::ash[] -include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/azurestack/04_bootstrap.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/upi/azurestack/04_bootstrap.json[] endif::ash[] ---- ==== diff --git a/modules/installation-arm-control-plane.adoc b/modules/installation-arm-control-plane.adoc index cff1aa1151..713277d2cb 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.18/upi/azure/05_masters.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/upi/azure/05_masters.json[] endif::ash[] ifdef::ash[] -include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/azurestack/05_masters.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/upi/azurestack/05_masters.json[] endif::ash[] ---- ==== diff --git a/modules/installation-arm-dns.adoc b/modules/installation-arm-dns.adoc index 6ae936edef..f44e3e1aa7 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.18/upi/azure/03_infra.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/upi/azure/03_infra.json[] endif::ash[] ifdef::ash[] -include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/azurestack/03_infra.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/upi/azurestack/03_infra.json[] endif::ash[] ---- ==== diff --git a/modules/installation-arm-image-storage.adoc b/modules/installation-arm-image-storage.adoc index 775e9175ec..f786b7b9bb 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.18/upi/azure/02_storage.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/upi/azure/02_storage.json[] endif::ash[] ifdef::ash[] -include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/azurestack/02_storage.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/upi/azurestack/02_storage.json[] endif::ash[] ---- ==== diff --git a/modules/installation-arm-vnet.adoc b/modules/installation-arm-vnet.adoc index 868d0df1f5..e68e6fb183 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.18/upi/azure/01_vnet.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/upi/azure/01_vnet.json[] endif::ash[] ifdef::ash[] -include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/azurestack/01_vnet.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/upi/azurestack/01_vnet.json[] endif::ash[] ---- ==== diff --git a/modules/installation-arm-worker.adoc b/modules/installation-arm-worker.adoc index 4f9e2849f1..991a652134 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.18/upi/azure/06_workers.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/upi/azure/06_workers.json[] endif::ash[] ifdef::ash[] -include::https://raw.githubusercontent.com/openshift/installer/release-4.18/upi/azurestack/06_workers.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/upi/azurestack/06_workers.json[] endif::ash[] ---- ==== diff --git a/modules/installation-aws-arm-tested-machine-types.adoc b/modules/installation-aws-arm-tested-machine-types.adoc index fe91514d6d..7e335701e3 100644 --- a/modules/installation-aws-arm-tested-machine-types.adoc +++ b/modules/installation-aws-arm-tested-machine-types.adoc @@ -23,5 +23,5 @@ Use the machine types included in the following charts for your AWS ARM instance .Machine types based on 64-bit ARM architecture [%collapsible] ==== -include::https://raw.githubusercontent.com/openshift/installer/release-4.18/docs/user/aws/tested_instance_types_aarch64.md[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/docs/user/aws/tested_instance_types_aarch64.md[] ==== diff --git a/modules/installation-aws-tested-machine-types.adoc b/modules/installation-aws-tested-machine-types.adoc index 5541585c40..6213bdaf96 100644 --- a/modules/installation-aws-tested-machine-types.adoc +++ b/modules/installation-aws-tested-machine-types.adoc @@ -47,7 +47,7 @@ ifndef::local-zone,wavelength-zone,secretregion[] .Machine types based on 64-bit x86 architecture [%collapsible] ==== -include::https://raw.githubusercontent.com/openshift/installer/release-4.18/docs/user/aws/tested_instance_types_x86_64.md[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/docs/user/aws/tested_instance_types_x86_64.md[] ==== endif::local-zone,wavelength-zone,secretregion[] ifdef::local-zone[] diff --git a/modules/installation-azure-arm-tested-machine-types.adoc b/modules/installation-azure-arm-tested-machine-types.adoc index 579787a23c..bc9bc8c5dd 100644 --- a/modules/installation-azure-arm-tested-machine-types.adoc +++ b/modules/installation-azure-arm-tested-machine-types.adoc @@ -19,5 +19,5 @@ The following Microsoft Azure ARM64 instance types have been tested with {produc .Machine types based on 64-bit ARM architecture [%collapsible] ==== -include::https://raw.githubusercontent.com/openshift/installer/release-4.18/docs/user/azure/tested_instance_types_aarch64.md[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/docs/user/azure/tested_instance_types_aarch64.md[] ==== diff --git a/modules/installation-cloudformation-bootstrap.adoc b/modules/installation-cloudformation-bootstrap.adoc index dda517113a..3636aacb21 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.18/upi/aws/cloudformation/04_cluster_bootstrap.yaml[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/upi/aws/cloudformation/04_cluster_bootstrap.yaml[] ---- ==== diff --git a/modules/installation-cloudformation-control-plane.adoc b/modules/installation-cloudformation-control-plane.adoc index f719347ccb..e2d98f7943 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.18/upi/aws/cloudformation/05_cluster_master_nodes.yaml[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/upi/aws/cloudformation/05_cluster_master_nodes.yaml[] ---- ==== diff --git a/modules/installation-cloudformation-dns.adoc b/modules/installation-cloudformation-dns.adoc index 8b4a8a365a..f2501cad99 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.18/upi/aws/cloudformation/02_cluster_infra.yaml[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/upi/aws/cloudformation/02_cluster_infra.yaml[] ---- ==== diff --git a/modules/installation-cloudformation-security.adoc b/modules/installation-cloudformation-security.adoc index 8d6c2c24ab..2136330ba8 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.18/upi/aws/cloudformation/03_cluster_security.yaml[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/upi/aws/cloudformation/03_cluster_security.yaml[] ---- ==== diff --git a/modules/installation-cloudformation-vpc.adoc b/modules/installation-cloudformation-vpc.adoc index a8775a950b..598da4d294 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.18/upi/aws/cloudformation/01_vpc.yaml[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/upi/aws/cloudformation/01_vpc.yaml[] ---- ==== diff --git a/modules/installation-cloudformation-worker.adoc b/modules/installation-cloudformation-worker.adoc index c3279e6e64..1dea93060f 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.18/upi/aws/cloudformation/06_cluster_worker_node.yaml[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/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 83baa49353..0311596bfd 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.18/upi/gcp/04_bootstrap.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/upi/gcp/04_bootstrap.py[] ---- ==== diff --git a/modules/installation-deployment-manager-control-plane.adoc b/modules/installation-deployment-manager-control-plane.adoc index fb55d64281..580fe3f9de 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.18/upi/gcp/05_control_plane.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/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 4e315147bf..429bf065a4 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.18/upi/gcp/02_lb_ext.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/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 3d7098ecc1..1e3ee736cf 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.18/upi/gcp/03_firewall.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/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 95ece6be76..1052abc053 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.18/upi/gcp/03_iam.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/upi/gcp/03_iam.py[] ---- ==== diff --git a/modules/installation-deployment-manager-int-lb.adoc b/modules/installation-deployment-manager-int-lb.adoc index 0da183704c..88789b2656 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.18/upi/gcp/02_lb_int.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/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 37f2b0180e..d9e09580b4 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.18/upi/gcp/02_dns.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/upi/gcp/02_dns.py[] ---- ==== diff --git a/modules/installation-deployment-manager-vpc.adoc b/modules/installation-deployment-manager-vpc.adoc index 822f49ce20..e74f7b8d4b 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.18/upi/gcp/01_vpc.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/upi/gcp/01_vpc.py[] ---- ==== diff --git a/modules/installation-deployment-manager-worker.adoc b/modules/installation-deployment-manager-worker.adoc index dc4afd5e52..563a85543b 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.18/upi/gcp/06_worker.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/upi/gcp/06_worker.py[] ---- ==== diff --git a/modules/installation-gcp-tested-machine-types-arm.adoc b/modules/installation-gcp-tested-machine-types-arm.adoc index cb881958ca..61f4f9c17d 100644 --- a/modules/installation-gcp-tested-machine-types-arm.adoc +++ b/modules/installation-gcp-tested-machine-types-arm.adoc @@ -18,5 +18,5 @@ The following Google Cloud Platform (GCP) 64-bit ARM instance types have been te .Machine series for 64-bit ARM machines [%collapsible] ==== -include::https://raw.githubusercontent.com/openshift/installer/release-4.18/docs/user/gcp/tested_instance_types_arm.md[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/docs/user/gcp/tested_instance_types_arm.md[] ==== \ No newline at end of file diff --git a/modules/installation-gcp-tested-machine-types.adoc b/modules/installation-gcp-tested-machine-types.adoc index 0da04bf2f7..cecebccd05 100644 --- a/modules/installation-gcp-tested-machine-types.adoc +++ b/modules/installation-gcp-tested-machine-types.adoc @@ -25,5 +25,5 @@ Some instance types require the use of Hyperdisk storage. If you use an instance .Machine series [%collapsible] ==== -include::https://raw.githubusercontent.com/openshift/installer/release-4.18/docs/user/gcp/tested_instance_types.md[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/docs/user/gcp/tested_instance_types.md[] ==== diff --git a/modules/installation-ibm-cloud-tested-machine-types.adoc b/modules/installation-ibm-cloud-tested-machine-types.adoc index 8e02b9ae0d..c5dfd3beb2 100644 --- a/modules/installation-ibm-cloud-tested-machine-types.adoc +++ b/modules/installation-ibm-cloud-tested-machine-types.adoc @@ -15,5 +15,5 @@ The following {ibm-cloud-name} instance types have been tested with {product-tit .Machine series [%collapsible] ==== -include::https://raw.githubusercontent.com/openshift/installer/release-4.18/docs/user/ibmcloud/tested_instance_types_x86_64.md[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.19/docs/user/ibmcloud/tested_instance_types_x86_64.md[] ==== \ No newline at end of file diff --git a/modules/installation-special-config-kmod.adoc b/modules/installation-special-config-kmod.adoc index fdefcf319e..4c0fbc5433 100644 --- a/modules/installation-special-config-kmod.adoc +++ b/modules/installation-special-config-kmod.adoc @@ -239,10 +239,10 @@ $ sudo spkut 44 .Example output [source,terminal] ---- -KVC: wrapper simple-kmod for 4.18.0-147.3.1.el8_1.x86_64 +KVC: wrapper simple-kmod for 4.19.0-147.3.1.el8_1.x86_64 Running userspace wrapper using the kernel module container... + podman run -i --rm --privileged - simple-kmod-dd1a7d4:4.18.0-147.3.1.el8_1.x86_64 spkut 44 + simple-kmod-dd1a7d4:4.19.0-147.3.1.el8_1.x86_64 spkut 44 simple-procfs-kmod number = 0 simple-procfs-kmod number = 44 ---- diff --git a/modules/installation-special-config-rtkernel.adoc b/modules/installation-special-config-rtkernel.adoc index 6b74266f75..d961f68603 100644 --- a/modules/installation-special-config-rtkernel.adoc +++ b/modules/installation-special-config-rtkernel.adoc @@ -120,7 +120,7 @@ sh-4.4# uname -a .Example output [source,terminal] ---- -Linux 4.18.0-147.3.1.rt24.96.el8_1.x86_64 #1 SMP PREEMPT RT +Linux 4.19.0-147.3.1.rt24.96.el8_1.x86_64 #1 SMP PREEMPT RT Wed Nov 27 18:29:55 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ---- + diff --git a/modules/installation-user-infra-machines-iso.adoc b/modules/installation-user-infra-machines-iso.adoc index fadebf9019..cbc99a8375 100644 --- a/modules/installation-user-infra-machines-iso.adoc +++ b/modules/installation-user-infra-machines-iso.adoc @@ -88,10 +88,10 @@ $ openshift-install coreos print-stream-json | grep '\.iso[^.]' [source,terminal] ifndef::openshift-origin[] ---- -"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", +"location": "/art/storage/releases/rhcos-4.19-aarch64//aarch64/rhcos--live.aarch64.iso", +"location": "/art/storage/releases/rhcos-4.19-ppc64le//ppc64le/rhcos--live.ppc64le.iso", +"location": "/art/storage/releases/rhcos-4.19-s390x//s390x/rhcos--live.s390x.iso", +"location": "/art/storage/releases/rhcos-4.19//x86_64/rhcos--live.x86_64.iso", ---- endif::openshift-origin[] ifdef::openshift-origin[] @@ -131,7 +131,7 @@ It is possible to interrupt the {op-system} installation boot process to add ker ---- ifdef::restricted[] $ sudo coreos-installer install --ignition-url=http:///.ign \ <1> ---ignition-hash=sha512- --offline <2> +--ignition-hash=sha512- --offline <2> endif::[] ifndef::restricted[] $ sudo coreos-installer install --ignition-url=http:///.ign \ <1> diff --git a/modules/installation-user-infra-machines-pxe.adoc b/modules/installation-user-infra-machines-pxe.adoc index c572d99b1c..4d7d2abc26 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.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" +"/art/storage/releases/rhcos-4.19-aarch64//aarch64/rhcos--live-kernel-aarch64" +"/art/storage/releases/rhcos-4.19-aarch64//aarch64/rhcos--live-initramfs.aarch64.img" +"/art/storage/releases/rhcos-4.19-aarch64//aarch64/rhcos--live-rootfs.aarch64.img" +"/art/storage/releases/rhcos-4.19-ppc64le/49.84.202110081256-0/ppc64le/rhcos--live-kernel-ppc64le" +"/art/storage/releases/rhcos-4.19-ppc64le//ppc64le/rhcos--live-initramfs.ppc64le.img" +"/art/storage/releases/rhcos-4.19-ppc64le//ppc64le/rhcos--live-rootfs.ppc64le.img" +"/art/storage/releases/rhcos-4.19-s390x//s390x/rhcos--live-kernel-s390x" +"/art/storage/releases/rhcos-4.19-s390x//s390x/rhcos--live-initramfs.s390x.img" +"/art/storage/releases/rhcos-4.19-s390x//s390x/rhcos--live-rootfs.s390x.img" +"/art/storage/releases/rhcos-4.19//x86_64/rhcos--live-kernel-x86_64" +"/art/storage/releases/rhcos-4.19//x86_64/rhcos--live-initramfs.x86_64.img" +"/art/storage/releases/rhcos-4.19//x86_64/rhcos--live-rootfs.x86_64.img" ---- endif::openshift-origin[] ifdef::openshift-origin[] diff --git a/modules/installing-a-cluster-with-multiarch-support.adoc b/modules/installing-a-cluster-with-multiarch-support.adoc index 1204f05478..8bcfad7774 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.18.0 +./openshift-install 4.19.0 built from commit abc123etc release image quay.io/openshift-release-dev/ocp-release@sha256:abc123wxyzetc release architecture multi @@ -31,7 +31,7 @@ default architecture amd64 + The output must contain `release architecture multi` to indicate that the `openshift-install` binary is using the `multi` payload. -. Update the `install-config.yaml` file to configure the architecture for the nodes. +. Update the `install-config.yaml` file to configure the architecture for the nodes. + .Sample `install-config.yaml` file with multi-architecture configuration + diff --git a/modules/k8s-nmstate-uninstall-operator.adoc b/modules/k8s-nmstate-uninstall-operator.adoc index c46fb6a34f..4a51eefe9f 100644 --- a/modules/k8s-nmstate-uninstall-operator.adoc +++ b/modules/k8s-nmstate-uninstall-operator.adoc @@ -6,7 +6,7 @@ [id="k8s-nmstate-uninstall-operator_{context}"] = Uninstalling the Kubernetes NMState Operator -You can use the {olm-first} to uninstall the Kubernetes NMState Operator, but by design {olm} does not delete any associated custom resource definitions (CRDs), custom resources (CRs), or API Services. +You can use the {olm-first} to uninstall the Kubernetes NMState Operator, but by design {olm} does not delete any associated custom resource definitions (CRDs), custom resources (CRs), or API Services. Before you uninstall the Kubernetes NMState Operator from the `Subcription` resource used by {olm}, identify what Kubernetes NMState Operator resources to delete. This identification ensures that you can delete resources without impacting your running cluster. @@ -38,14 +38,14 @@ $ oc get --namespace openshift-nmstate clusterserviceversion [source,terminal] ---- NAME DISPLAY VERSION REPLACES PHASE -kubernetes-nmstate-operator.v4.18.0 Kubernetes NMState Operator 4.18.0 Succeeded +kubernetes-nmstate-operator.v4.19.0 Kubernetes NMState Operator 4.19.0 Succeeded ---- . Delete the CSV resource. After you delete the file, {olm} deletes certain resources, such as `RBAC`, that it created for the Operator. + [source,terminal] ---- -$ oc delete --namespace openshift-nmstate clusterserviceversion kubernetes-nmstate-operator.v4.18.0 +$ oc delete --namespace openshift-nmstate clusterserviceversion kubernetes-nmstate-operator.v4.19.0 ---- . Delete the `nmstate` CR and any associated `Deployment` resources by running the following commands: @@ -105,4 +105,3 @@ $ oc delete crd nodenetworkconfigurationpolicies.nmstate.io ---- $ oc delete namespace kubernetes-nmstate ---- - diff --git a/modules/logging-loki-storage-odf.adoc b/modules/logging-loki-storage-odf.adoc index 3fe69f83bf..5a4c13b1b5 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.18/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/latest/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 2f5463c8ce..6dd837d1ec 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.18.0 quay.io/openshift-release-dev/ocp-release@sha256:6a899c54dda6b844bb12a247e324a0f6cde367e880b73ba110c056df6d018032 +4.19.0 quay.io/openshift-release-dev/ocp-release@sha256:6a899c54dda6b844bb12a247e324a0f6cde367e880b73ba110c056df6d018032 ... ---- diff --git a/modules/migration-configuring-mcg.adoc b/modules/migration-configuring-mcg.adoc index a14bae6b81..e6b05ec609 100644 --- a/modules/migration-configuring-mcg.adoc +++ b/modules/migration-configuring-mcg.adoc @@ -42,7 +42,7 @@ ifdef::installing-3-4,installing-mtc[] You use these credentials to add MCG as a replication repository. endif::[] ifdef::installing-oadp-mcg[] -. Create an MCG bucket. For more information, see link:https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.18/html-single/managing_hybrid_and_multicloud_resources/index[Managing hybrid and multicloud resources]. +. Create an MCG bucket. For more information, see link:https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/latest/html-single/managing_hybrid_and_multicloud_resources/index[Managing hybrid and multicloud resources]. . Obtain the S3 endpoint, `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, and the bucket name by running the `oc describe` command on the bucket resource. diff --git a/modules/mirror-registry-release-notes.adoc b/modules/mirror-registry-release-notes.adoc index c88891b19b..562b46858b 100644 --- a/modules/mirror-registry-release-notes.adoc +++ b/modules/mirror-registry-release-notes.adoc @@ -94,7 +94,7 @@ The following advisory is available for the _mirror registry for Red{nbsp}Hat Op [id="mirror-registry-new-features-2-0_{context}"] ==== New features -* With the release of _mirror registry for Red{nbsp}Hat OpenShift_, the internal database has been upgraded from PostgreSQL to SQLite. As a result, data is now stored on the `sqlite-storage` Podman volume by default, and the overall tarball size is reduced by 300 MB. +* With the release of _mirror registry for Red{nbsp}Hat OpenShift_, the internal database has been upgraded from PostgreSQL to SQLite. As a result, data is now stored on the `sqlite-storage` Podman volume by default, and the overall tarball size is reduced by 300 MB. + New installations use SQLite by default. Before upgrading to version 2.0, see "Updating mirror registry for Red Hat OpenShift from a local host" or "Updating mirror registry for Red Hat OpenShift from a remote host" depending on your environment. @@ -105,7 +105,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.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]. +To view the _mirror registry for Red{nbsp}Hat OpenShift_ 1.3 release notes, see link:https://docs.openshift.com/container-platform/4.19/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/multi-architecture-scheduling.adoc b/modules/multi-architecture-scheduling.adoc index 3cbfe837c5..4ee6bcd915 100644 --- a/modules/multi-architecture-scheduling.adoc +++ b/modules/multi-architecture-scheduling.adoc @@ -7,5 +7,5 @@ When you deploy workloads on a cluster with compute nodes that use different arc You can use the Multiarch Tuning Operator to enable architecture-aware scheduling of workloads on clusters with multi-architecture compute machines. The Multiarch Tuning Operator implements additional scheduler predicates in the pods specifications based on the architectures that the pods can support at creation time. ifndef::openshift-enterprise[] -For information about the Multiarch Tuning Operator, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/postinstallation_configuration/configuring-multi-architecture-compute-machines-on-an-openshift-cluster#multiarch-tuning-operator[Managing workloads on multi-architecture clusters by using the Multiarch Tuning Operator]. +For information about the Multiarch Tuning Operator, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html/postinstallation_configuration/configuring-multi-architecture-compute-machines-on-an-openshift-cluster#multiarch-tuning-operator[Managing workloads on multi-architecture clusters by using the Multiarch Tuning Operator]. endif::openshift-enterprise[] \ No newline at end of file diff --git a/modules/nodes-nodes-viewing-listing.adoc b/modules/nodes-nodes-viewing-listing.adoc index 3915e7f788..c3da7ae16e 100644 --- a/modules/nodes-nodes-viewing-listing.adoc +++ b/modules/nodes-nodes-viewing-listing.adoc @@ -60,9 +60,9 @@ $ oc get nodes -o wide [source,terminal] ---- NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME -master.example.com Ready master 171m v1.32.3 10.0.129.108 Red Hat Enterprise Linux CoreOS 48.83.202103210901-0 (Ootpa) 4.18.0-240.15.1.el8_3.x86_64 cri-o://1.32.3-30.rhaos4.10.gitf2f339d.el8-dev -node1.example.com Ready worker 72m v1.32.3 10.0.129.222 Red Hat Enterprise Linux CoreOS 48.83.202103210901-0 (Ootpa) 4.18.0-240.15.1.el8_3.x86_64 cri-o://1.32.3-30.rhaos4.10.gitf2f339d.el8-dev -node2.example.com Ready worker 164m v1.32.3 10.0.142.150 Red Hat Enterprise Linux CoreOS 48.83.202103210901-0 (Ootpa) 4.18.0-240.15.1.el8_3.x86_64 cri-o://1.32.3-30.rhaos4.10.gitf2f339d.el8-dev +master.example.com Ready master 171m v1.32.3 10.0.129.108 Red Hat Enterprise Linux CoreOS 48.83.202103210901-0 (Ootpa) 4.19.0-240.15.1.el8_3.x86_64 cri-o://1.32.3-30.rhaos4.10.gitf2f339d.el8-dev +node1.example.com Ready worker 72m v1.32.3 10.0.129.222 Red Hat Enterprise Linux CoreOS 48.83.202103210901-0 (Ootpa) 4.19.0-240.15.1.el8_3.x86_64 cri-o://1.32.3-30.rhaos4.10.gitf2f339d.el8-dev +node2.example.com Ready worker 164m v1.32.3 10.0.142.150 Red Hat Enterprise Linux CoreOS 48.83.202103210901-0 (Ootpa) 4.19.0-240.15.1.el8_3.x86_64 cri-o://1.32.3-30.rhaos4.10.gitf2f339d.el8-dev ---- * The following command lists information about a single node: diff --git a/modules/nw-dpu-operator-uninstall.adoc b/modules/nw-dpu-operator-uninstall.adoc index a07680f03c..ba7ad4cbe8 100644 --- a/modules/nw-dpu-operator-uninstall.adoc +++ b/modules/nw-dpu-operator-uninstall.adoc @@ -50,14 +50,14 @@ $ oc get csv -n openshift-dpu-operator [source,terminal] ---- NAME DISPLAY VERSION REPLACES PHASE -dpu-operator.v4.18.0-202503130333 DPU Operator 4.18.0-202503130333 Failed +dpu-operator.v4.19.0-202503130333 DPU Operator 4.19.0-202503130333 Failed ---- .. Delete the DPU Operator by running the following command: + [source,terminal] ---- -$ oc delete csv dpu-operator.v4.18.0-202503130333 -n openshift-dpu-operator +$ oc delete csv dpu-operator.v4.19.0-202503130333 -n openshift-dpu-operator ---- . Delete the namespace that was created for the DPU Operator by running the following command: diff --git a/modules/oadp-gcp-wif-cloud-authentication.adoc b/modules/oadp-gcp-wif-cloud-authentication.adoc index dcb747e496..f0fdae664b 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.18/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/latest/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 aa9fed35df..6079bcde95 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.18 <1> - minVersion: 4.18.2 - maxVersion: 4.18.2 + - name: stable-4.19 <1> + minVersion: 4.19.2 + maxVersion: 4.19.2 graph: true <2> operators: - - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.18 <3> + - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.19 <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 0cbcc9e9f2..49104d43d6 100644 --- a/modules/oc-mirror-image-set-config-examples.adoc +++ b/modules/oc-mirror-image-set-config-examples.adoc @@ -254,7 +254,7 @@ mirror: The following `ImageSetConfiguration` file includes the `eus-` channel, where the `maxVersion` value is at least two minor versions higher than the `minVersion` value. -For example, in this `ImageSetConfiguration` file, the `minVersion` is set to `4.12.28`, while the `maxVersion` for the `eus-4.14` channel is `4.14.16`. +For example, in this `ImageSetConfiguration` file, the `minVersion` is set to `4.12.28`, while the `maxVersion` for the `eus-4.14` channel is `4.14.16`. .Example `ImageSetConfiguration` file [source,yaml,subs="attributes+"] @@ -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.18.0` in the channel. +The following `ImageSetConfiguration` file includes {mce} and all {product-title} versions starting at a minimum version of `{product-version}.0` in the channel. .Example `ImageSetConfiguration` file [source,yaml,subs=attributes+] @@ -298,12 +298,12 @@ mirror: architectures: - "multi" channels: - - name: stable-4.18 - minVersion: 4.18.0 - maxVersion: 4.18.1 + - name: stable-4.19 + minVersion: 4.19.0 + maxVersion: 4.19.1 type: ocp operators: - - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.18 + - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.19 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 c676981bd5..b5b56ce227 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.18`. +|String. For example: `registry.redhat.io/redhat/redhat-operator-index:v{product-version}`. |`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.18`. +|String. For example: `fast` or `stable-v{product-version}`. |`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.18` +|String. For example: `stable-{product-version}` |`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.18.1` +|String. For example: `{product-version}.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 088cbe2572..bd7bb7cc4d 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.18/web_console/adding-user-preferences.html[Adding User Preferences] for more information on changing perspectives. +See link:https://docs.openshift.com/container-platform/latest/web_console/adding-user-preferences.html[Adding User Preferences] for more information on changing perspectives. .Procedure diff --git a/modules/osd-lifecycle-policy.adoc b/modules/osd-lifecycle-policy.adoc index 326ba04ee4..6acd93b463 100644 --- a/modules/osd-lifecycle-policy.adoc +++ b/modules/osd-lifecycle-policy.adoc @@ -9,7 +9,4 @@ To plan an upgrade, review the _{product-title} update life cycle_ guide in the "Additional resources" section. The life cycle page includes release definitions, support and upgrade requirements, installation policy information, and life cycle dates. -You can use update channels to decide which Red Hat OpenShift Container Platform minor version to update your clusters to. {product-title} supports updates only through the `stable` channel. To learn more about OpenShift update channels and releases, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/updating_clusters/understanding-openshift-updates-1#understanding-update-channels-releases[Understanding update channels and releases]. - - - +You can use update channels to decide which Red Hat OpenShift Container Platform minor version to update your clusters to. {product-title} supports updates only through the `stable` channel. To learn more about OpenShift update channels and releases, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html/updating_clusters/understanding-openshift-updates-1#understanding-update-channels-releases[Understanding update channels and releases]. diff --git a/modules/registry-configuring-registry-storage-rhodf-cephfs.adoc b/modules/registry-configuring-registry-storage-rhodf-cephfs.adoc index a94e87671a..9d4793a501 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.18[{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/latest[{rh-storage} Operator] to provide object storage and CephFS file storage. .Procedure @@ -58,4 +58,3 @@ EOF ---- $ oc patch config.image/cluster -p '{"spec":{"managementState":"Managed","replicas":2,"storage":{"managementState":"Unmanaged","pvc":{"claim":"registry-storage-pvc"}}}}' --type=merge ---- - diff --git a/modules/registry-configuring-registry-storage-rhodf-cephrgw.adoc b/modules/registry-configuring-registry-storage-rhodf-cephrgw.adoc index d499bb8512..af33dfe0cf 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.18[{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/latest[{rh-storage} Operator] to provide object storage and Ceph RGW object storage. .Procedure @@ -96,5 +96,3 @@ $ oc create configmap image-registry-s3-bundle --from-file=ca-bundle.crt=./tls.c ---- $ oc patch config.image/cluster -p '{"spec":{"managementState":"Managed","replicas":2,"storage":{"managementState":"Unmanaged","s3":{"bucket":'\"${bucket_name}\"',"region":"us-east-1","regionEndpoint":'\"https://${route_host}\"',"virtualHostedStyle":false,"encrypt":false,"trustedCA":{"name":"image-registry-s3-bundle"}}}}}' --type=merge ---- - - diff --git a/modules/registry-configuring-registry-storage-rhodf-nooba.adoc b/modules/registry-configuring-registry-storage-rhodf-nooba.adoc index 63cccb1317..614502fa64 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.18[{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/latest[{rh-storage} Operator] to provide object storage and Noobaa object storage. .Procedure @@ -93,4 +93,3 @@ $ oc create configmap image-registry-s3-bundle --from-file=ca-bundle.crt=./tls.c ---- $ oc patch config.image/cluster -p '{"spec":{"managementState":"Managed","replicas":2,"storage":{"managementState":"Unmanaged","s3":{"bucket":'\"${bucket_name}\"',"region":"us-east-1","regionEndpoint":'\"https://${route_host}\"',"virtualHostedStyle":false,"encrypt":false,"trustedCA":{"name":"image-registry-s3-bundle"}}}}}' --type=merge ---- - diff --git a/modules/rosa-create-objects.adoc b/modules/rosa-create-objects.adoc index f321828c6b..437282faab 100644 --- a/modules/rosa-create-objects.adoc +++ b/modules/rosa-create-objects.adoc @@ -317,7 +317,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.18.0`. For `account-role` use an `X.Y` format, for example, `4.18`. +|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.19.0`. For `account-role` use an `X.Y` format, for example, `4.19`. |--worker-iam-role string |The ARN of the IAM role that will be attached to compute instances. @@ -385,7 +385,7 @@ $ rosa create external-auth-provider --cluster= | [ar |=== |Option |Definition -|--claim-mapping-groups-claim +|--claim-mapping-groups-claim |Required. Describes rules on how to transform information from an ID token into a cluster identity. |--claim-validation-rule @@ -400,7 +400,7 @@ a|--cluster \| |--console-client-id |The identifier of the OIDC client from the OIDC provider for the {cluster-manager-url} web console. -|--console-client-secret +|--console-client-secret |The secret that is associated with the console application registration. |--issuer-audiences @@ -669,7 +669,7 @@ $ rosa create ingress --cluster=mycluster --label-match=foo=bar,bar=baz [id="rosa-create-kubeletconfig_{context}"] == create kubeletconfig -Create a custom `KubeletConfig` object to allow custom configuration of nodes in a +Create a custom `KubeletConfig` object to allow custom configuration of nodes in a ifdef::temp-ifdef[] cluster. endif::[] @@ -791,7 +791,7 @@ The default value is `0`, meaning that no outdated nodes are removed before new |--replicas |Required when autoscaling is not configured. The number (integer) of machines for this machine pool. -|--tags +|--tags |Apply user defined tags to all resources created by ROSA in AWS. Tags are comma separated, for example: `'key value, foo bar'`. |--taints 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 30442bb12c..eb3c65ea9e 100644 --- a/modules/rosa-deleting-account-wide-iam-roles-and-policies.adoc +++ b/modules/rosa-deleting-account-wide-iam-roles-and-policies.adoc @@ -15,30 +15,30 @@ endif::[] [id="rosa-deleting-account-wide-iam-roles-and-policies_{context}"] = Deleting the account-wide IAM roles and policies -This section provides steps to delete the account-wide IAM roles and policies that you created for +This section provides steps to delete the account-wide IAM roles and policies that you created for ifdef::sts[] -ROSA with STS +ROSA with STS endif::sts[] ifdef::hcp[] -{hcp-title} -endif::hcp[] -deployments, along with the account-wide Operator policies. You can delete the account-wide AWS Identity and Access Management (IAM) roles and policies only after deleting all of the +{hcp-title} +endif::hcp[] +deployments, along with the account-wide Operator policies. You can delete the account-wide AWS Identity and Access Management (IAM) roles and policies only after deleting all of the ifdef::sts[] -{product-title} (ROSA) with AWS Security Token Services (STS) +{product-title} (ROSA) with AWS Security Token Services (STS) endif::sts[] ifdef::hcp[] -{hcp-title} +{hcp-title} endif::hcp[] clusters that depend on them. [IMPORTANT] ==== -The account-wide IAM roles and policies might be used by other +The account-wide IAM roles and policies might be used by other ifdef::sts[] -ROSA clusters +ROSA clusters endif::sts[] ifdef::hcp[] -{product-title} +{product-title} endif::hcp[] in the same AWS account. Only remove the roles if they are not required by other clusters. ==== @@ -64,10 +64,10 @@ ifdef::sts[] ---- I: Fetching account roles ROLE NAME ROLE TYPE ROLE ARN OPENSHIFT VERSION -ManagedOpenShift-ControlPlane-Role Control plane arn:aws:iam:::role/ManagedOpenShift-ControlPlane-Role 4.10 -ManagedOpenShift-Installer-Role Installer arn:aws:iam:::role/ManagedOpenShift-Installer-Role 4.10 -ManagedOpenShift-Support-Role Support arn:aws:iam:::role/ManagedOpenShift-Support-Role 4.10 -ManagedOpenShift-Worker-Role Worker arn:aws:iam:::role/ManagedOpenShift-Worker-Role 4.10 +ManagedOpenShift-ControlPlane-Role Control plane arn:aws:iam:::role/ManagedOpenShift-ControlPlane-Role 4.19 +ManagedOpenShift-Installer-Role Installer arn:aws:iam:::role/ManagedOpenShift-Installer-Role 4.19 +ManagedOpenShift-Support-Role Support arn:aws:iam:::role/ManagedOpenShift-Support-Role 4.19 +ManagedOpenShift-Worker-Role Worker arn:aws:iam:::role/ManagedOpenShift-Worker-Role 4.19 ---- endif::sts[] ifdef::hcp[] @@ -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.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 +ManagedOpenShift-HCP-ROSA-Installer-Role Installer arn:aws:iam:::role/ManagedOpenShift-HCP-ROSA-Installer-Role 4.19 Yes +ManagedOpenShift-HCP-ROSA-Support-Role Support arn:aws:iam:::role/ManagedOpenShift-HCP-ROSA-Support-Role 4.19 Yes +ManagedOpenShift-HCP-ROSA-Worker-Role Worker arn:aws:iam:::role/ManagedOpenShift-HCP-ROSA-Worker-Role 4.19 Yes ---- endif::hcp[] .. Delete the account-wide roles: @@ -121,12 +121,12 @@ If you did not specify a custom prefix when you created the account-wide roles, + [IMPORTANT] ==== -The account-wide in-line and Operator IAM policies might be used by other +The account-wide in-line and Operator IAM policies might be used by other ifdef::sts[] -ROSA clusters +ROSA clusters endif::sts[] ifdef::hcp[] -{hcp-title} +{hcp-title} endif::hcp[] in the same AWS account. Only remove the roles if they are not required by other clusters. ==== diff --git a/modules/rosa-hcp-deleting-cluster.adoc b/modules/rosa-hcp-deleting-cluster.adoc index 3a66138606..9665957fd6 100644 --- a/modules/rosa-hcp-deleting-cluster.adoc +++ b/modules/rosa-hcp-deleting-cluster.adoc @@ -40,13 +40,13 @@ Display Name: test_cluster ID: <1> External ID: Control Plane: ROSA Service Hosted -OpenShift Version: 4.18.0 +OpenShift Version: 4.19.0 Channel Group: stable DNS: test_cluster.l3cn.p3.openshiftapps.com AWS Account: AWS Billing Account: API URL: https://api.test_cluster.l3cn.p3.openshiftapps.com:443 -Console URL: +Console URL: Region: us-east-1 Availability: - Control Plane: MultiAZ @@ -77,7 +77,7 @@ Operator IAM Roles: <2> - arn:aws:iam:::role/hcpcluster-kube-system-kms-provider - arn:aws:iam:::role/test_cluster-openshift-cluster-csi-drivers-ebs-cloud-credentials Managed Policies: Yes -State: ready +State: ready Private: No Created: Apr 16 2024 20:32:06 UTC User Workload Monitoring: Enabled 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 e8935e5e51..f27cd31743 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 @@ -22,7 +22,7 @@ When creating a {hcp-title} cluster, the default machine Classless Inter-Domain + [source,terminal] ---- -$ rosa create cluster --hosted-cp --subnet-ids=$SUBNET_IDS \ +$ rosa create cluster --hosted-cp --subnet-ids=$SUBNET_IDS \ --oidc-config-id=$OIDC_ID --cluster-name= \ --operator-roles-prefix=$OPERATOR_ROLES_PREFIX \ --external-auth-providers-enabled @@ -56,7 +56,7 @@ Display Name: rosa-ext-test ID: External ID: Control Plane: ROSA Service Hosted -OpenShift Version: 4.18.0 +OpenShift Version: 4.19.0 Channel Group: stable DNS: AWS Account: diff --git a/modules/rosa-sts-account-wide-roles-and-policies.adoc b/modules/rosa-sts-account-wide-roles-and-policies.adoc index a629e1fec9..66fa4e824b 100644 --- a/modules/rosa-sts-account-wide-roles-and-policies.adoc +++ b/modules/rosa-sts-account-wide-roles-and-policies.adoc @@ -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.18/sts_installer_trust_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.19/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.18/sts_installer_permission_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.19/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.18/sts_instance_controlplane_trust_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.19/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.18/sts_instance_controlplane_permission_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.19/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.18/sts_instance_worker_trust_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.19/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.18/sts_instance_worker_permission_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.19/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.18/sts_support_trust_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.19/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.18/sts_support_permission_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.19/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.18/sts_ocm_trust_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.19/sts_ocm_trust_policy.json[] ---- ==== @@ -197,18 +197,18 @@ 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.18/sts_installer_trust_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.19/sts_installer_trust_policy.json[] ---- ==== [discrete] [id="rosa-sts-account-wide-roles-and-policies-example-cli-output-for-policies-attached-to-a-role_{context}"] -==== Example CLI output for policies attached to a role +==== Example CLI output for policies attached to a role When a policy is attached to a role, the ROSA CLI displays a confirmation output. The output depends on the type of policy. * If the policy is a trust policy, the ROSA CLI outputs the role name and the content of the policy. -** For the target role with policy attached, ROSA CLI outputs the role name and the console URL of the target role. +** For the target role with policy attached, ROSA CLI outputs the role name and the console URL of the target role. + .Target role with policy attached example output [source,terminal] @@ -221,7 +221,7 @@ I: Attached trust policy to role 'testrole-Worker-Role(https://console.aws.amazo .Trust policy example output [source,terminal] ---- -I: Attached trust policy to role 'test-Support-Role': {"Version": "2012-10-17", "Statement": [{"Action": ["sts:AssumeRole"], "Effect": "Allow", "Principal": {"AWS": ["arn:aws:iam::000000000000:role/RH-Technical-Support-00000000"]}}]} +I: Attached trust policy to role 'test-Support-Role': {"Version": "2012-10-17", "Statement": [{"Action": ["sts:AssumeRole"], "Effect": "Allow", "Principal": {"AWS": ["arn:aws:iam::000000000000:role/RH-Technical-Support-00000000"]}}]} ---- * If the policy is a permission policy, the ROSA CLI outputs the name and public link of this policy or the ARN depending on whether or not the policy is an AWS managed policy or customer-managed policy. ** If the attached policy is an AWS managed policy, the ROSA CLI outputs the name and public link of this policy and the role it is attached to. @@ -229,14 +229,14 @@ I: Attached trust policy to role 'test-Support-Role': {"Version": "2012-10-17", .AWS managed policy example output [source,terminal] ---- -I: Attached policy 'ROSASRESupportPolicy(https://docs.aws.amazon.com/aws-managed-policy/latest/reference/ROSASRESupportPolicy)' to role 'test-HCP-ROSA-Support-Role(https://console.aws.amazon.com/iam/home?#/roles/test-HCP-ROSA-Support-Role)' +I: Attached policy 'ROSASRESupportPolicy(https://docs.aws.amazon.com/aws-managed-policy/latest/reference/ROSASRESupportPolicy)' to role 'test-HCP-ROSA-Support-Role(https://console.aws.amazon.com/iam/home?#/roles/test-HCP-ROSA-Support-Role)' ---- ** If the attached policy is an AWS managed policy, the ROSA CLI outputs the name and public link of this policy and the role it is attached to. + .Customer-managed policy example output [source,terminal] ---- -I: Attached policy 'arn:aws:iam::000000000000:policy/testrole-Worker-Role-Policy' to role 'testrole-Worker-Role(https://console.aws.amazon.com/iam/home?#/roles/testrole-Worker-Role)' +I: Attached policy 'arn:aws:iam::000000000000:policy/testrole-Worker-Role-Policy' to role 'testrole-Worker-Role(https://console.aws.amazon.com/iam/home?#/roles/testrole-Worker-Role)' ---- .ROSA Ingress Operator IAM policy and policy file @@ -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.18/openshift_ingress_operator_cloud_credentials_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.19/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.18/openshift_cluster_csi_drivers_ebs_cloud_credentials_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.19/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.18/openshift_machine_api_aws_cloud_credentials_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.19/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.18/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.19/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.18/openshift_image_registry_installer_cloud_credentials_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.19/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 500c73ba99..9c4580be01 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.18/sts_installer_core_permission_boundary_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.19/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.18/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.19/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.18/sts_installer_privatelink_permission_boundary_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.19/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.18/sts_installer_vpc_permission_boundary_policy.json[] +include::https://raw.githubusercontent.com/openshift/managed-cluster-config/refs/heads/master/resources/sts/4.19/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 426bbb5dca..7e1bcff2ec 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.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> + 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.19.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.18.0`. +<4> When creating the cluster, the listed `OpenShift version` options include the major, minor, and patch versions, for example `4.19.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 fb7a706b10..f75a87ed5f 100644 --- a/modules/sd-understanding-process-id-limits.adoc +++ b/modules/sd-understanding-process-id-limits.adoc @@ -43,7 +43,7 @@ endif::openshift-enterprise,openshift-origin[] ifdef::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[] * Maximum number of PIDs per 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. +The default value depends on link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.19/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. endif::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[] 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 464fdf23d1..973d0ce05f 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.18 + 4.19 test diff --git a/modules/verifying-cluster-install-oci-agent-based.adoc b/modules/verifying-cluster-install-oci-agent-based.adoc index 113d731c19..0fca2a4dba 100644 --- a/modules/verifying-cluster-install-oci-agent-based.adoc +++ b/modules/verifying-cluster-install-oci-agent-based.adoc @@ -100,9 +100,9 @@ $ oc get co [source,terminal] ---- NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE -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: … +authentication 4.19.0-0 True False False 6m18s +baremetal 4.19.0-0 True False False 2m42s +network 4.19.0-0 True True False 5m58s Progressing: … … ---- diff --git a/modules/virt-checking-storage-configuration.adoc b/modules/virt-checking-storage-configuration.adoc index c44c99890b..d5fb5739d9 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.18.2 # <5> + status.result.cnvVersion: 4.19.2 # <5> status.result.defaultStorageClass: trident-nfs <6> status.result.goldenImagesNoDataSource: # <7> status.result.goldenImagesNotUpToDate: # <8> - status.result.ocpVersion: 4.18.0 # <9> + status.result.ocpVersion: 4.19.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 2b85c78f23..1276c6dce2 100644 --- a/modules/virt-metro-dr-odf.adoc +++ b/modules/virt-metro-dr-odf.adoc @@ -6,16 +6,16 @@ [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.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. +{VirtProductName} supports the link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/latest/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. +* This synchronous solution is only available to metropolitan distance data centers with a network round-trip latency of 10 milliseconds or less. * Multiple disk VMs are supported. -* To prevent data corruption, you must ensure that storage is fenced during failover. +* To prevent data corruption, you must ensure that storage is fenced during failover. + [TIP] ==== -Fencing means isolating a node so that workloads do not run on it. +Fencing means isolating a node so that workloads do not run on it. ==== For more information about using the Metro-DR solution for {rh-storage} with {VirtProductName}, see {ibm-title}'s {rh-storage} Metro-DR documentation. \ No newline at end of file diff --git a/modules/virt-regional-dr-odf.adoc b/modules/virt-regional-dr-odf.adoc index c608247f44..96570ced39 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.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. +{VirtProductName} supports the link:https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/latest/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 61607832b5..4774f45166 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 @@ -203,7 +203,7 @@ spec: fieldRef: fieldPath: spec.nodeName image: >- - quay.io/openshift-virtualization/wasp-agent:v4.18 <1> + quay.io/openshift-virtualization/wasp-agent:v4.19 <1> imagePullPolicy: Always name: wasp-agent resources: @@ -282,7 +282,7 @@ $ oc label namespace wasp openshift.io/cluster-monitoring="true" -- * Web console + -. In the {product-title} web console, go to *Virtualization* -> *Overview* -> *Settings* -> *General settings* -> *Memory density*. +. In the {product-title} web console, go to *Virtualization* -> *Overview* -> *Settings* -> *General settings* -> *Memory density*. . Set *Enable memory density* to on. * CLI diff --git a/modules/ztp-image-based-upgrade-procedure-rollback.adoc b/modules/ztp-image-based-upgrade-procedure-rollback.adoc index 37877fd10d..71e4f03ce2 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.18.0-rc.1 - version: 4.18.0-rc.1 + image: quay.io/seed/image:4.19.0-rc.1 + version: 4.19.0-rc.1 pullSecretRef: name: "" extraManifests: @@ -59,7 +59,7 @@ spec: $ oc apply -f .yaml ---- -All managed clusters that match the defined labels are moved back to the `Rollback` and then the `Idle` stages to finalize the rollback. +All managed clusters that match the defined labels are moved back to the `Rollback` and then the `Idle` stages to finalize the rollback. -- .Verification diff --git a/modules/ztp-sno-accelerated-ztp.adoc b/modules/ztp-sno-accelerated-ztp.adoc index bbc1c138c5..7cadb0ba4f 100644 --- a/modules/ztp-sno-accelerated-ztp.adoc +++ b/modules/ztp-sno-accelerated-ztp.adoc @@ -9,8 +9,8 @@ :FeatureName: Accelerated provisioning of {ztp} include::snippets/technology-preview.adoc[] -You can reduce the time taken for cluster installation by using accelerated provisioning of {ztp} for {sno}. -Accelerated ZTP speeds up installation by applying Day 2 manifests derived from policies at an earlier stage. +You can reduce the time taken for cluster installation by using accelerated provisioning of {ztp} for {sno}. +Accelerated ZTP speeds up installation by applying Day 2 manifests derived from policies at an earlier stage. [IMPORTANT] ==== @@ -34,7 +34,7 @@ spec: baseDomain: "example.com" pullSecretRef: name: "assisted-deployment-pull-secret" - clusterImageSetNameRef: "openshift-4.18" + clusterImageSetNameRef: "openshift-4.19" sshPublicKey: "ssh-rsa AAAA..." clusters: # ... @@ -46,8 +46,8 @@ spec: ---- -You can use `accelerated-ztp: full` to fully automate the accelerated process. -{ztp} updates the `AgentClusterInstall` resource with a reference to the accelerated {ztp} `ConfigMap`, and includes resources extracted from policies by {cgu-operator}, and accelerated ZTP job manifests. +You can use `accelerated-ztp: full` to fully automate the accelerated process. +{ztp} updates the `AgentClusterInstall` resource with a reference to the accelerated {ztp} `ConfigMap`, and includes resources extracted from policies by {cgu-operator}, and accelerated ZTP job manifests. If you use `accelerated-ztp: partial`, {ztp} does not include the accelerated job manifests, but includes policy-derived objects created during the cluster installation of the following `kind` types: @@ -57,11 +57,11 @@ If you use `accelerated-ztp: partial`, {ztp} does not include the accelerated jo * `CatalogSource.operators.coreos.com` * `ContainerRuntimeConfig.machineconfiguration.openshift.io` -This partial acceleration can reduce the number of reboots done by the node when applying resources of the kind `Performance Profile`, `Tuned`, and `ContainerRuntimeConfig`. +This partial acceleration can reduce the number of reboots done by the node when applying resources of the kind `Performance Profile`, `Tuned`, and `ContainerRuntimeConfig`. {cgu-operator} installs the Operator subscriptions derived from policies after {rh-rhacm} completes the import of the cluster, following the same flow as standard {ztp}. -The benefits of accelerated ZTP increase with the scale of your deployment. -Using `accelerated-ztp: full` gives more benefit on a large number of clusters. +The benefits of accelerated ZTP increase with the scale of your deployment. +Using `accelerated-ztp: full` gives more benefit on a large number of clusters. With a smaller number of clusters, the reduction in installation time is less significant. Full accelerated ZTP leaves behind a namespace and a completed job on the spoke that need to be manually removed. @@ -70,11 +70,11 @@ One benefit of using `accelerated-ztp: partial` is that you can override the fun [id="the-accelerated-ztp-process_{context}"] == The accelerated ZTP process -Accelerated ZTP uses an additional `ConfigMap` to create the resources derived from policies on the spoke cluster. -The standard `ConfigMap` includes manifests that the {ztp} workflow uses to customize cluster installs. +Accelerated ZTP uses an additional `ConfigMap` to create the resources derived from policies on the spoke cluster. +The standard `ConfigMap` includes manifests that the {ztp} workflow uses to customize cluster installs. {cgu-operator} detects that the `accelerated-ztp` label is set and then creates a second `ConfigMap`. -As part of accelerated ZTP, the `SiteConfig` generator adds a reference to that second `ConfigMap` using the naming convention `-aztp`. +As part of accelerated ZTP, the `SiteConfig` generator adds a reference to that second `ConfigMap` using the naming convention `-aztp`. -After {cgu-operator} creates that second `ConfigMap`, it finds all policies bound to the managed cluster and extracts the {ztp} profile information. -{cgu-operator} adds the {ztp} profile information to the `-aztp` `ConfigMap` custom resource (CR) and applies the CR to the hub cluster API. +After {cgu-operator} creates that second `ConfigMap`, it finds all policies bound to the managed cluster and extracts the {ztp} profile information. +{cgu-operator} adds the {ztp} profile information to the `-aztp` `ConfigMap` custom resource (CR) and applies the CR to the hub cluster API. diff --git a/modules/ztp-sno-siteconfig-config-reference.adoc b/modules/ztp-sno-siteconfig-config-reference.adoc index 4e9803bc63..3fbf9af620 100644 --- a/modules/ztp-sno-siteconfig-config-reference.adoc +++ b/modules/ztp-sno-siteconfig-config-reference.adoc @@ -49,7 +49,7 @@ a|Configure this field to enable disk encryption with Trusted Platform Module (T [NOTE] ==== -Configuring disk encryption by using the `diskEncryption` field in the `SiteConfig` CR is a Technology Preview feature in {product-title} 4.18. +Configuring disk encryption by using the `diskEncryption` field in the `SiteConfig` CR is a Technology Preview feature in {product-title} 4.19. ==== |`spec.clusters.diskEncryption.type` diff --git a/osd_planning/gcp-ccs.adoc b/osd_planning/gcp-ccs.adoc index 195baa506b..33aaeb4bf2 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.18/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.19/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 4744b2118e..48b30faea3 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.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/documentation/en-us/red_hat_openshift_data_foundation/latest/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 d1cd042c67..c947abed42 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.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/documentation/en-us/red_hat_openshift_data_foundation/latest/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 29f2c9b0b3..c13c9c6620 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.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/documentation/en-us/red_hat_openshift_data_foundation/latest/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 0b483f85ae..0db765a534 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.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/documentation/en-us/red_hat_openshift_data_foundation/latest/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/scalability_and_performance/telco-hub-rds.adoc b/scalability_and_performance/telco-hub-rds.adoc index 44da30bec4..c3ca7a5d36 100644 --- a/scalability_and_performance/telco-hub-rds.adoc +++ b/scalability_and_performance/telco-hub-rds.adoc @@ -7,7 +7,7 @@ include::_attributes/common-attributes.adoc[] toc::[] -The telco hub reference design specifications (RDS) describes the configuration for a hub cluster that deploys and operates fleets of {product-title} clusters in a telco environment. +The telco hub reference design specifications (RDS) describes the configuration for a hub cluster that deploys and operates fleets of {product-title} clusters in a telco environment. :FeatureName: The telco hub RDS include::snippets/technology-preview.adoc[] @@ -94,7 +94,7 @@ include::modules/telco-hub-storage-considerations.adoc[leveloffset=+2] .Additional resources * xref:../storage/understanding-persistent-storage.adoc#persistent-storage-overview_understanding-persistent-storage[Persistent storage overview] -* link:https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.18/html/red_hat_openshift_data_foundation_architecture/index[{rh-storage} architecture] +* link:https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/latest/html/red_hat_openshift_data_foundation_architecture/index[{rh-storage} architecture] * xref:../storage/persistent_storage/persistent_storage_local/persistent-storage-local.adoc#persistent-storage-using-local-volume[Persistent storage using local volumes] * xref:../scalability_and_performance/recommended-performance-scale-practices/recommended-etcd-practices.adoc#recommended-etcd-practices[Recommended etcd practices] diff --git a/snippets/ibu-ImageBasedGroupUpgrade.adoc b/snippets/ibu-ImageBasedGroupUpgrade.adoc index 7ff07b47da..b4db01a766 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.18.0-rc.1 - version: 4.18.0-rc.1 + image: quay.io/seed/image:4.19.0-rc.1 + version: 4.19.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 7fe747cf27..b159db09bd 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.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. +Familiarity with link:https://access.redhat.com/documentation/en-us/openshift_container_platform/latest/html-single/storage/index#persistent-storage-overview_understanding-persistent-storage[persistent storage] and link:https://access.redhat.com/documentation/en-us/openshift_container_platform/latest/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,4 @@ 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.18/html-single/storage/index#persistent-storage-csi[Configuring CSI volumes] - +* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/latest/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 7d063d4894..935850f0f9 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.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. +Familiarity with link:https://access.redhat.com/documentation/en-us/openshift_container_platform/latest/html-single/storage/index#persistent-storage-overview_understanding-persistent-storage[persistent storage] and link:https://access.redhat.com/documentation/en-us/openshift_container_platform/latest/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.18/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/latest/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,4 @@ 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.18/html-single/storage/index#persistent-storage-csi[Configuring CSI volumes] - +* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/latest/html-single/storage/index#persistent-storage-csi[Configuring CSI volumes] diff --git a/support/approved-access.adoc b/support/approved-access.adoc index 28437a09f0..8bccac4352 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.18/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/latest/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 bc0f26e536..c70faa8a24 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.18/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/latest/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/creating_vms_advanced/creating_vms_cli/virt-creating-vms-by-cloning-pvcs.adoc b/virt/creating_vms_advanced/creating_vms_cli/virt-creating-vms-by-cloning-pvcs.adoc index 7d66d8318b..ab5f818377 100644 --- a/virt/creating_vms_advanced/creating_vms_cli/virt-creating-vms-by-cloning-pvcs.adoc +++ b/virt/creating_vms_advanced/creating_vms_cli/virt-creating-vms-by-cloning-pvcs.adoc @@ -36,8 +36,8 @@ include::modules/virt-optimizing-clone-performance-at-scale-in-openshift-data-fo [role="_additional-resources"] .Additional resources * xref:../../../virt/storage/virt-configuring-storage-profile.adoc#virt-customizing-storage-profile-default-cloning-strategy_virt-configuring-storage-profile[Setting a default cloning strategy using a storage profile] -* link:https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.18/html/managing_and_allocating_storage_resources/volume-cloning_rhodf#volume-cloning_rhodf[Volume cloning] -* link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html/storage/using-container-storage-interface-csi#persistent-storage-csi-snapshots[CSI volume snapshots] +* link:https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/latest/html/managing_and_allocating_storage_resources/volume-cloning_rhodf#volume-cloning_rhodf[Volume cloning] +* link:https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html/storage/using-container-storage-interface-csi#persistent-storage-csi-snapshots[CSI volume snapshots] include::modules/virt-cloning-pvc-to-dv-cli.adoc[leveloffset=+2] diff --git a/virt/support/virt-collecting-virt-data.adoc b/virt/support/virt-collecting-virt-data.adoc index 9b1ff9703d..f36b03c82e 100644 --- a/virt/support/virt-collecting-virt-data.adoc +++ b/virt/support/virt-collecting-virt-data.adoc @@ -50,7 +50,7 @@ endif::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[] // must-gather not supported for ROSA/OSD, per Dustin Row ifndef::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[] . 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.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. +. link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/latest/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/accessing-metrics/accessing-metrics-as-an-administrator.adoc#querying-metrics-for-all-projects-with-mon-dashboard_accessing-metrics-as-an-administrator[Collect Prometheus metrics for the cluster]. endif::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]