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 54484e2e03..b5ef85f330 100644 --- a/authentication/assuming-an-aws-iam-role-for-a-service-account.adoc +++ b/authentication/assuming-an-aws-iam-role-for-a-service-account.adoc @@ -38,5 +38,5 @@ include::modules/verifying-the-assumed-iam-role-in-your-pod.adoc[leveloffset=+2] * For more information about installing and using the AWS Boto3 SDK for Python, see the link:https://boto3.amazonaws.com/v1/documentation/api/latest/index.html[AWS Boto3 documentation]. ifdef::openshift-rosa,openshift-dedicated[] -* For general information about webhook admission plugins for OpenShift, see link:https://docs.openshift.com/container-platform/4.15/architecture/admission-plug-ins.html#admission-webhooks-about_admission-plug-ins[Webhook admission plugins] in the OpenShift Container Platform documentation. +* For general information about webhook admission plugins for OpenShift, see link:https://docs.openshift.com/container-platform/4.16/architecture/admission-plug-ins.html#admission-webhooks-about_admission-plug-ins[Webhook admission plugins] in the OpenShift Container Platform documentation. endif::openshift-rosa,openshift-dedicated[] diff --git a/installing/install_config/enabling-cgroup-v1.adoc b/installing/install_config/enabling-cgroup-v1.adoc index f9df5f7c68..9824f23511 100644 --- a/installing/install_config/enabling-cgroup-v1.adoc +++ b/installing/install_config/enabling-cgroup-v1.adoc @@ -7,7 +7,7 @@ include::_attributes/common-attributes.adoc[] toc::[] -As of {product-title} 4.14, {product-title} uses link:https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html[Linux control group version 2] (cgroup v2) in your cluster. If you are using cgroup v1 on {product-title} 4.13 or earlier, migrating to {product-title} 4.15 will not automatically update your cgroup configuration to version 2. A fresh installation of {product-title} 4.14 or later will use cgroup v2 by default. However, you can enable link:https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v1/index.html[Linux control group version 1] (cgroup v1) upon installation. Enabling cgroup v1 in {product-title} disables all cgroup v2 controllers and hierarchies in your cluster. +As of {product-title} 4.14, {product-title} uses link:https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html[Linux control group version 2] (cgroup v2) in your cluster. If you are using cgroup v1 on {product-title} 4.13 or earlier, migrating to {product-title} {product-version} will not automatically update your cgroup configuration to version 2. A fresh installation of {product-title} 4.14 or later will use cgroup v2 by default. However, you can enable link:https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v1/index.html[Linux control group version 1] (cgroup v1) upon installation. Enabling cgroup v1 in {product-title} disables all cgroup v2 controllers and hierarchies in your cluster. :FeatureName: cgroup v1 include::snippets/deprecated-feature.adoc[] diff --git a/microshift_cli_ref/microshift-cli-tools-introduction.adoc b/microshift_cli_ref/microshift-cli-tools-introduction.adoc index 892df03d33..bff9a0e0a5 100644 --- a/microshift_cli_ref/microshift-cli-tools-introduction.adoc +++ b/microshift_cli_ref/microshift-cli-tools-introduction.adoc @@ -24,6 +24,6 @@ Commands for multi-node deployments, projects, and developer tooling are not sup == Additional resources * xref:..//microshift_cli_ref/microshift-oc-cli-install.adoc#microshift-oc-cli-install[Installing the OpenShift CLI tool for MicroShift]. -* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.15/html/cli_tools/openshift-cli-oc[Detailed description of the OpenShift CLI (oc)]. +* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.16/html/cli_tools/openshift-cli-oc[Detailed description of the OpenShift CLI (oc)]. * link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9[Red Hat Enterprise Linux (RHEL) documentation for specific use cases]. * xref:../microshift_configuring/microshift-cluster-access-kubeconfig.adoc#microshift-kubeconfig[Cluster access with kubeconfig] \ No newline at end of file diff --git a/microshift_networking/microshift_multiple_networks/microshift-cni-multus-using.adoc b/microshift_networking/microshift_multiple_networks/microshift-cni-multus-using.adoc index 7b2076f5b6..a2d55f9403 100644 --- a/microshift_networking/microshift_multiple_networks/microshift-cni-multus-using.adoc +++ b/microshift_networking/microshift_multiple_networks/microshift-cni-multus-using.adoc @@ -26,4 +26,4 @@ include::modules/microshift-cni-multus-troubleshoot.adoc[leveloffset=+1] == Additional resources * xref:../../microshift_networking/microshift_multiple_networks/microshift-cni-multus.adoc#microshift-cni-multus[About using multiple networks] -* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.15/html/networking/multiple-networks#nw-multus-ipam-object_configuring-additional-network[Configuration of IP address assignment for an additional network] \ No newline at end of file +* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.16/html/networking/multiple-networks#nw-multus-ipam-object_configuring-additional-network[Configuration of IP address assignment for an additional network] \ No newline at end of file diff --git a/modules/about-developer-perspective.adoc b/modules/about-developer-perspective.adoc index b063e37d76..7dbc79b56c 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.15/applications/odc-viewing-application-composition-using-topology-view.html[Viewing application composition using the Topology] view for more information on using the *Topology* view in *Developer* perspective. +See link:https://docs.openshift.com/container-platform/4.16/applications/odc-viewing-application-composition-using-topology-view.html[Viewing application composition using the Topology] view for more information on using the *Topology* view in *Developer* perspective. diff --git a/modules/cpmso-openstack-with-az-config.adoc b/modules/cpmso-openstack-with-az-config.adoc index 7ec7027719..28f9b244a9 100644 --- a/modules/cpmso-openstack-with-az-config.adoc +++ b/modules/cpmso-openstack-with-az-config.adoc @@ -43,7 +43,7 @@ providerSpec: name: openstack-cloud-credentials namespace: openshift-machine-api flavor: m1.xlarge - image: rhcos-4.15 + image: rhcos-4.16 kind: OpenstackProviderSpec metadata: creationTimestamp: null diff --git a/modules/creating-config-files-cluster-install-oci.adoc b/modules/creating-config-files-cluster-install-oci.adoc index fe314d57ee..6a8b8e5dca 100644 --- a/modules/creating-config-files-cluster-install-oci.adoc +++ b/modules/creating-config-files-cluster-install-oci.adoc @@ -38,9 +38,9 @@ $ ./openshift-install version .Example output for a shared registry binary [source,terminal,subs="quotes"] ---- -./openshift-install 4.15.0 +./openshift-install 4.16.0 built from commit ae7977b7d1ca908674a0d45c5c243c766fa4b2ca -release image registry.ci.openshift.org/origin/release:4.15ocp-release@sha256:0da6316466d60a3a4535d5fed3589feb0391989982fba59d47d4c729912d6363 +release image registry.ci.openshift.org/origin/release:4.16ocp-release@sha256:0da6316466d60a3a4535d5fed3589feb0391989982fba59d47d4c729912d6363 release architecture amd64 ---- ==== diff --git a/modules/hosted-control-planes-version-support.adoc b/modules/hosted-control-planes-version-support.adoc index 28be2770a0..313cecfb66 100644 --- a/modules/hosted-control-planes-version-support.adoc +++ b/modules/hosted-control-planes-version-support.adoc @@ -22,7 +22,7 @@ You can host different versions of control planes on the same management cluster ---- apiVersion: v1 data: - supported-versions: '{"versions":["4.15"]}' + supported-versions: '{"versions":["4.16"]}' kind: ConfigMap metadata: labels: diff --git a/modules/insights-operator-one-time-gather.adoc b/modules/insights-operator-one-time-gather.adoc index e25ef62f76..8313258613 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.15/docs/gather-job.yaml[] +include::https://raw.githubusercontent.com/openshift/insights-operator/release-4.16/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 7d370f0e2a..42a3553857 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.15/upi/azure/04_bootstrap.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/upi/azure/04_bootstrap.json[] endif::ash[] ifdef::ash[] -include::https://raw.githubusercontent.com/openshift/installer/release-4.15/upi/azurestack/04_bootstrap.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/upi/azurestack/04_bootstrap.json[] endif::ash[] ---- ==== diff --git a/modules/installation-arm-control-plane.adoc b/modules/installation-arm-control-plane.adoc index e39c8656f8..28e1b84df8 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.15/upi/azure/05_masters.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/upi/azure/05_masters.json[] endif::ash[] ifdef::ash[] -include::https://raw.githubusercontent.com/openshift/installer/release-4.15/upi/azurestack/05_masters.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/upi/azurestack/05_masters.json[] endif::ash[] ---- ==== diff --git a/modules/installation-arm-dns.adoc b/modules/installation-arm-dns.adoc index c767e54d3d..7049e4ebf1 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.15/upi/azure/03_infra.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/upi/azure/03_infra.json[] endif::ash[] ifdef::ash[] -include::https://raw.githubusercontent.com/openshift/installer/release-4.15/upi/azurestack/03_infra.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/upi/azurestack/03_infra.json[] endif::ash[] ---- ==== diff --git a/modules/installation-arm-image-storage.adoc b/modules/installation-arm-image-storage.adoc index f5627f78a8..5039aaf70d 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.15/upi/azure/02_storage.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/upi/azure/02_storage.json[] endif::ash[] ifdef::ash[] -include::https://raw.githubusercontent.com/openshift/installer/release-4.15/upi/azurestack/02_storage.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/upi/azurestack/02_storage.json[] endif::ash[] ---- ==== diff --git a/modules/installation-arm-vnet.adoc b/modules/installation-arm-vnet.adoc index b9130e79b5..7fdf18d43a 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.15/upi/azure/01_vnet.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/upi/azure/01_vnet.json[] endif::ash[] ifdef::ash[] -include::https://raw.githubusercontent.com/openshift/installer/release-4.15/upi/azurestack/01_vnet.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/upi/azurestack/01_vnet.json[] endif::ash[] ---- ==== diff --git a/modules/installation-arm-worker.adoc b/modules/installation-arm-worker.adoc index 3966a73010..276dbed7f2 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.15/upi/azure/06_workers.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/upi/azure/06_workers.json[] endif::ash[] ifdef::ash[] -include::https://raw.githubusercontent.com/openshift/installer/release-4.15/upi/azurestack/06_workers.json[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/upi/azurestack/06_workers.json[] endif::ash[] ---- ==== diff --git a/modules/installation-cloudformation-bootstrap.adoc b/modules/installation-cloudformation-bootstrap.adoc index c7fce6247e..2b509ba5a5 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.15/upi/aws/cloudformation/04_cluster_bootstrap.yaml[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/upi/aws/cloudformation/04_cluster_bootstrap.yaml[] ---- ==== diff --git a/modules/installation-cloudformation-control-plane.adoc b/modules/installation-cloudformation-control-plane.adoc index 735119d573..3dd5d5c787 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.15/upi/aws/cloudformation/05_cluster_master_nodes.yaml[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/upi/aws/cloudformation/05_cluster_master_nodes.yaml[] ---- ==== diff --git a/modules/installation-cloudformation-dns.adoc b/modules/installation-cloudformation-dns.adoc index a285b88c40..a438273a94 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.15/upi/aws/cloudformation/02_cluster_infra.yaml[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/upi/aws/cloudformation/02_cluster_infra.yaml[] ---- ==== diff --git a/modules/installation-cloudformation-security.adoc b/modules/installation-cloudformation-security.adoc index 4fa7f8899a..98698a4612 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.15/upi/aws/cloudformation/03_cluster_security.yaml[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/upi/aws/cloudformation/03_cluster_security.yaml[] ---- ==== diff --git a/modules/installation-cloudformation-vpc.adoc b/modules/installation-cloudformation-vpc.adoc index 426237718b..3a2661b171 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.15/upi/aws/cloudformation/01_vpc.yaml[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/upi/aws/cloudformation/01_vpc.yaml[] ---- ==== diff --git a/modules/installation-cloudformation-worker.adoc b/modules/installation-cloudformation-worker.adoc index 8c9e71011a..6bec122b83 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.15/upi/aws/cloudformation/06_cluster_worker_node.yaml[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/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 1375d54523..56b5096fe9 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.15/upi/gcp/04_bootstrap.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/upi/gcp/04_bootstrap.py[] ---- ==== diff --git a/modules/installation-deployment-manager-control-plane.adoc b/modules/installation-deployment-manager-control-plane.adoc index 6e9e12b12c..a9de670172 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.15/upi/gcp/05_control_plane.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/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 803507d584..3edbf1a0c2 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.15/upi/gcp/02_lb_ext.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/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 96baed7642..3608861774 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.15/upi/gcp/03_firewall.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/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 18742d3775..cebdffd316 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.15/upi/gcp/03_iam.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/upi/gcp/03_iam.py[] ---- ==== diff --git a/modules/installation-deployment-manager-int-lb.adoc b/modules/installation-deployment-manager-int-lb.adoc index 1fc098a08c..97ebf20b8d 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.15/upi/gcp/02_lb_int.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/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 c48c478496..b6a19b5808 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.15/upi/gcp/02_dns.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/upi/gcp/02_dns.py[] ---- ==== diff --git a/modules/installation-deployment-manager-vpc.adoc b/modules/installation-deployment-manager-vpc.adoc index 6f5b604152..b5e24890ea 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.15/upi/gcp/01_vpc.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/upi/gcp/01_vpc.py[] ---- ==== diff --git a/modules/installation-deployment-manager-worker.adoc b/modules/installation-deployment-manager-worker.adoc index 03bc880671..f287a58931 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.15/upi/gcp/06_worker.py[] +include::https://raw.githubusercontent.com/openshift/installer/release-4.16/upi/gcp/06_worker.py[] ---- ==== diff --git a/modules/installation-gcp-user-infra-rhcos.adoc b/modules/installation-gcp-user-infra-rhcos.adoc index 5135333490..1582ec7235 100644 --- a/modules/installation-gcp-user-infra-rhcos.adoc +++ b/modules/installation-gcp-user-infra-rhcos.adoc @@ -12,7 +12,7 @@ your {product-title} nodes. .Procedure ifndef::openshift-origin[] -. Obtain the {op-system} image from the link:https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/4.15/[{op-system} image mirror] page. +. Obtain the {op-system} image from the link:https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/4.16/[{op-system} image mirror] page. + [IMPORTANT] ==== diff --git a/modules/installation-user-infra-machines-iso.adoc b/modules/installation-user-infra-machines-iso.adoc index 7bea85e9ba..aecf008c32 100644 --- a/modules/installation-user-infra-machines-iso.adoc +++ b/modules/installation-user-infra-machines-iso.adoc @@ -85,10 +85,10 @@ $ openshift-install coreos print-stream-json | grep '\.iso[^.]' [source,terminal] ifndef::openshift-origin[] ---- -"location": "/art/storage/releases/rhcos-4.15-aarch64//aarch64/rhcos--live.aarch64.iso", -"location": "/art/storage/releases/rhcos-4.15-ppc64le//ppc64le/rhcos--live.ppc64le.iso", -"location": "/art/storage/releases/rhcos-4.15-s390x//s390x/rhcos--live.s390x.iso", -"location": "/art/storage/releases/rhcos-4.15//x86_64/rhcos--live.x86_64.iso", +"location": "/art/storage/releases/rhcos-4.16-aarch64//aarch64/rhcos--live.aarch64.iso", +"location": "/art/storage/releases/rhcos-4.16-ppc64le//ppc64le/rhcos--live.ppc64le.iso", +"location": "/art/storage/releases/rhcos-4.16-s390x//s390x/rhcos--live.s390x.iso", +"location": "/art/storage/releases/rhcos-4.16//x86_64/rhcos--live.x86_64.iso", ---- endif::openshift-origin[] ifdef::openshift-origin[] diff --git a/modules/installation-user-infra-machines-pxe.adoc b/modules/installation-user-infra-machines-pxe.adoc index 707e6e0ba6..b5bf251c97 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.15-aarch64//aarch64/rhcos--live-kernel-aarch64" -"/art/storage/releases/rhcos-4.15-aarch64//aarch64/rhcos--live-initramfs.aarch64.img" -"/art/storage/releases/rhcos-4.15-aarch64//aarch64/rhcos--live-rootfs.aarch64.img" -"/art/storage/releases/rhcos-4.15-ppc64le/49.84.202110081256-0/ppc64le/rhcos--live-kernel-ppc64le" -"/art/storage/releases/rhcos-4.15-ppc64le//ppc64le/rhcos--live-initramfs.ppc64le.img" -"/art/storage/releases/rhcos-4.15-ppc64le//ppc64le/rhcos--live-rootfs.ppc64le.img" -"/art/storage/releases/rhcos-4.15-s390x//s390x/rhcos--live-kernel-s390x" -"/art/storage/releases/rhcos-4.15-s390x//s390x/rhcos--live-initramfs.s390x.img" -"/art/storage/releases/rhcos-4.15-s390x//s390x/rhcos--live-rootfs.s390x.img" -"/art/storage/releases/rhcos-4.15//x86_64/rhcos--live-kernel-x86_64" -"/art/storage/releases/rhcos-4.15//x86_64/rhcos--live-initramfs.x86_64.img" -"/art/storage/releases/rhcos-4.15//x86_64/rhcos--live-rootfs.x86_64.img" +"/art/storage/releases/rhcos-4.16-aarch64//aarch64/rhcos--live-kernel-aarch64" +"/art/storage/releases/rhcos-4.16-aarch64//aarch64/rhcos--live-initramfs.aarch64.img" +"/art/storage/releases/rhcos-4.16-aarch64//aarch64/rhcos--live-rootfs.aarch64.img" +"/art/storage/releases/rhcos-4.16-ppc64le/49.84.202110081256-0/ppc64le/rhcos--live-kernel-ppc64le" +"/art/storage/releases/rhcos-4.16-ppc64le//ppc64le/rhcos--live-initramfs.ppc64le.img" +"/art/storage/releases/rhcos-4.16-ppc64le//ppc64le/rhcos--live-rootfs.ppc64le.img" +"/art/storage/releases/rhcos-4.16-s390x//s390x/rhcos--live-kernel-s390x" +"/art/storage/releases/rhcos-4.16-s390x//s390x/rhcos--live-initramfs.s390x.img" +"/art/storage/releases/rhcos-4.16-s390x//s390x/rhcos--live-rootfs.s390x.img" +"/art/storage/releases/rhcos-4.16//x86_64/rhcos--live-kernel-x86_64" +"/art/storage/releases/rhcos-4.16//x86_64/rhcos--live-initramfs.x86_64.img" +"/art/storage/releases/rhcos-4.16//x86_64/rhcos--live-rootfs.x86_64.img" ---- endif::openshift-origin[] ifdef::openshift-origin[] diff --git a/modules/installation-vsphere-machines.adoc b/modules/installation-vsphere-machines.adoc index d331dc3015..90cba21cb8 100644 --- a/modules/installation-vsphere-machines.adoc +++ b/modules/installation-vsphere-machines.adoc @@ -79,7 +79,7 @@ If you plan to add more compute machines to your cluster after you finish instal ==== ifndef::openshift-origin[] -. Obtain the {op-system} OVA image. Images are available from the link:https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/4.15/[{op-system} image mirror] page. +. Obtain the {op-system} OVA image. Images are available from the link:https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/4.16/[{op-system} image mirror] page. + [IMPORTANT] ==== diff --git a/modules/k8s-nmstate-deploying-nmstate-CLI.adoc b/modules/k8s-nmstate-deploying-nmstate-CLI.adoc index 60d611848b..977795038b 100644 --- a/modules/k8s-nmstate-deploying-nmstate-CLI.adoc +++ b/modules/k8s-nmstate-deploying-nmstate-CLI.adoc @@ -84,7 +84,7 @@ $ oc get clusterserviceversion -n openshift-nmstate \ [source, terminal,subs="attributes+"] ---- Name Phase -kubernetes-nmstate-operator.4.15.0-202210210157 Succeeded +kubernetes-nmstate-operator.4.16.0-202210210157 Succeeded ---- . Create an instance of the `nmstate` Operator: diff --git a/modules/logging-loki-storage-odf.adoc b/modules/logging-loki-storage-odf.adoc index dc6e321aff..ca63c7d126 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.15/html/managing_and_allocating_storage_resources/adding-file-and-object-storage-to-an-existing-external-ocs-cluster[for object storage]. +* You configured your {rh-storage} cluster link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.16/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 f1d721468f..ed946477f7 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.15.0 quay.io/openshift-release-dev/ocp-release@sha256:6a899c54dda6b844bb12a247e324a0f6cde367e880b73ba110c056df6d018032 +4.16.0 quay.io/openshift-release-dev/ocp-release@sha256:6a899c54dda6b844bb12a247e324a0f6cde367e880b73ba110c056df6d018032 ... ---- diff --git a/modules/microshift-adding-service-to-blueprint.adoc b/modules/microshift-adding-service-to-blueprint.adoc index 96deaa63dd..1b35bec459 100644 --- a/modules/microshift-adding-service-to-blueprint.adoc +++ b/modules/microshift-adding-service-to-blueprint.adoc @@ -48,7 +48,7 @@ EOF + [NOTE] ==== -The wildcard `*` in the commands uses the latest {microshift-short} RPMs. If you need a specific version, substitute the wildcard for the version you want. For example, insert `4.15.0` to download the {microshift-short} 4.15.0 RPMs. +The wildcard `*` in the commands uses the latest {microshift-short} RPMs. If you need a specific version, substitute the wildcard for the version you want. For example, insert `4.16.0` to download the {microshift-short} 4.16.0 RPMs. ==== . Optional. Use the blueprint installed in the `/usr/share/microshift/blueprint` directory that is specific to your platform architecture. See the following example snippet for an explanation of the blueprint sections: @@ -58,14 +58,14 @@ The wildcard `*` in the commands uses the latest {microshift-short} RPMs. If you [source,text] ---- name = "microshift_blueprint" -description = "MicroShift 4.15.1 on x86_64 platform" +description = "MicroShift 4.16.1 on x86_64 platform" version = "0.0.1" modules = [] groups = [] [[packages]] <1> name = "microshift" -version = "4.15.1" +version = "4.16.1" ... ... @@ -115,11 +115,11 @@ $ sudo composer-cli blueprints depsolve ____ | grep micros [source,terminal] ---- blueprint: microshift_blueprint v0.0.1 - microshift-greenboot-4.15.1-202305250827.p0.g4105d3b.assembly.4.15.1.el9.noarch - microshift-networking-4.15.1-202305250827.p0.g4105d3b.assembly.4.15.1.el9.x86_64 - microshift-release-info-4.15.1-202305250827.p0.g4105d3b.assembly.4.15.1.el9.noarch - microshift-4.15.1-202305250827.p0.g4105d3b.assembly.4.15.1.el9.x86_64 - microshift-selinux-4.15.1-202305250827.p0.g4105d3b.assembly.4.15.1.el9.noarch + microshift-greenboot-4.16.1-202305250827.p0.g4105d3b.assembly.4.16.1.el9.noarch + microshift-networking-4.16.1-202305250827.p0.g4105d3b.assembly.4.16.1.el9.x86_64 + microshift-release-info-4.16.1-202305250827.p0.g4105d3b.assembly.4.16.1.el9.noarch + microshift-4.16.1-202305250827.p0.g4105d3b.assembly.4.16.1.el9.x86_64 + microshift-selinux-4.16.1-202305250827.p0.g4105d3b.assembly.4.16.1.el9.noarch ---- //need updated example output . Optional: Verify the Image Builder configuration listing all components to be installed by running the following command: diff --git a/modules/microshift-embed-microshift-image-offline-deploy.adoc b/modules/microshift-embed-microshift-image-offline-deploy.adoc index 33ca895a62..0fb5ec30dc 100644 --- a/modules/microshift-embed-microshift-image-offline-deploy.adoc +++ b/modules/microshift-embed-microshift-image-offline-deploy.adoc @@ -28,7 +28,7 @@ You can use Image Builder to create `rpm-ostree` system images with embedded {mi ---- $ sudo dnf install -y microshift-release-info- ---- -Replace `` with the numerical value of the release you are deploying, using the entire version number, such as `4.15.0`. +Replace `` with the numerical value of the release you are deploying, using the entire version number, such as `4.16.0`. .. List the contents of the `/usr/share/microshift/release` directory to verify the presence of the release information files by running the following command: + @@ -54,14 +54,14 @@ If you installed the `microshift-release-info` RPM, you can proceed to step 4. ---- $ sudo dnf download microshift-release-info- ---- -Replace `` with the numerical value of the release you are deploying, using the entire version number, such as `4.15.0`. +Replace `` with the numerical value of the release you are deploying, using the entire version number, such as `4.16.0`. + .Example rpm [source,terminal] ---- -microshift-release-info-4.15.0.*.el9.noarch.rpm <1> +microshift-release-info-4.16.0.*.el9.noarch.rpm <1> ---- -<1> The `*` represents the date and commit ID. Your output should contain both, for example `-202311101230.p0.g7dc6a00.assembly.4.15.0`. +<1> The `*` represents the date and commit ID. Your output should contain both, for example `-202311101230.p0.g7dc6a00.assembly.4.16.0`. .. Unpack the RPM package without installing it by running the following command: + diff --git a/modules/microshift-etcd-version.adoc b/modules/microshift-etcd-version.adoc index 9e3f7aabd5..445e91d919 100644 --- a/modules/microshift-etcd-version.adoc +++ b/modules/microshift-etcd-version.adoc @@ -21,7 +21,7 @@ $ microshift-etcd version .Example output [source,terminal,subs="attributes+"] ---- -microshift-etcd Version: 4.15.1 +microshift-etcd Version: 4.16.1 Base etcd Version: 3.5.10 ---- @@ -38,7 +38,7 @@ $ microshift-etcd version -o json { "major": "4", "minor": "15", - "gitVersion": "4.15.1", + "gitVersion": "4.16.1", "gitCommit": "2e182312718cc9d267ec71f37dc2fbe2eed01ee2", "gitTreeState": "clean", "buildDate": "2024-01-09T06:51:40Z", diff --git a/modules/microshift-oc-mirror-creating-imageset-config.adoc b/modules/microshift-oc-mirror-creating-imageset-config.adoc index ba29f94a12..d87688ee6d 100644 --- a/modules/microshift-oc-mirror-creating-imageset-config.adoc +++ b/modules/microshift-oc-mirror-creating-imageset-config.adoc @@ -41,10 +41,10 @@ storageConfig: mirror: platform: # <1> channels: - - name: stable-4.15 + - name: stable-4.16 type: ocp operators: - - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.15 + - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.16 packages: - name: serverless-operator channels: @@ -70,7 +70,7 @@ storageConfig: <1> skipTLS: false mirror: operators: - - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.15 <3> + - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.16 <3> packages: - name: amq-broker-rhel8 <4> channels: diff --git a/modules/microshift-oc-mirror-embed-ops-disconnected-use.adoc b/modules/microshift-oc-mirror-embed-ops-disconnected-use.adoc index feecec7306..bd26f1b46c 100644 --- a/modules/microshift-oc-mirror-embed-ops-disconnected-use.adoc +++ b/modules/microshift-oc-mirror-embed-ops-disconnected-use.adoc @@ -27,14 +27,14 @@ For catalogs made for proprietary Operators, you can format image references for + [source,terminal] ---- -jq -r --slurp '.[] | select(.relatedImages != null) | "[[containers]]\nsource = \"" + .relatedImages[].image + "\"\n"' ./oc-mirror-workspace/src/catalogs/registry.redhat.io/redhat/redhat-operator-index/v4.15/index/index.json +jq -r --slurp '.[] | select(.relatedImages != null) | "[[containers]]\nsource = \"" + .relatedImages[].image + "\"\n"' ./oc-mirror-workspace/src/catalogs/registry.redhat.io/redhat/redhat-operator-index/v4.16/index/index.json ---- .. If you want to filter out images that cannot be mirrored, filter and parse the catalog `index.json` file by running the following command: + [source,terminal] ---- -$ jq -r --slurp '.[] | select(.relatedImages != null) | .relatedImages[] | select(.name | contains("ppc") or contains("s390x") | not) | "[[containers]]\\nsource = \\"" + .image + "\\"\\n"' ./oc-mirror-workspace/src/catalogs/registry.redhat.io/redhat/redhat-operator-index/v4.15/index/index.json +$ jq -r --slurp '.[] | select(.relatedImages != null) | .relatedImages[] | select(.name | contains("ppc") or contains("s390x") | not) | "[[containers]]\\nsource = \\"" + .image + "\\"\\n"' ./oc-mirror-workspace/src/catalogs/registry.redhat.io/redhat/redhat-operator-index/v4.16/index/index.json ---- + [NOTE] @@ -84,21 +84,21 @@ storageConfig: imageURL: registry.example.com/microshift-mirror mirror: operators: - - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.15 <1> + - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.16 <1> packages: - name: amq-broker-rhel8 channels: - name: 7.11.x ---- -<1> Use the value in the `mirror.catalog` catalog image reference for the follwing `jq` command to get the image digest. In this example, __. +<1> Use the value in the `mirror.catalog` catalog image reference for the follwing `jq` command to get the image digest. In this example, __. . Get the SHA of the catalog index image by running the following command: + [source,terminal] ---- -$ skopeo inspect docker:// | jq `.Digest` <1> +$ skopeo inspect docker:// | jq `.Digest` <1> ---- -<1> Use the value in the `mirror.catalog` catalog image reference for the `jq` command to get the image digest. In this example, __. +<1> Use the value in the `mirror.catalog` catalog image reference for the `jq` command to get the image digest. In this example, __. + .Example output [source,terminal] @@ -120,14 +120,14 @@ source = "registry.redhat.io/redhat/redhat-operator-index@sha256:7a76c0880a83903 [source,text] ---- name = "microshift_blueprint" -description = "MicroShift 4.15.1 on x86_64 platform" +description = "MicroShift 4.16.1 on x86_64 platform" version = "0.0.1" modules = [] groups = [] [[packages]] <1> name = "microshift" -version = "4.15.1" +version = "4.16.1" ... ... diff --git a/modules/microshift-oc-mirror-install-catalog-cluster.adoc b/modules/microshift-oc-mirror-install-catalog-cluster.adoc index 61f94c09b7..d16a4c0945 100644 --- a/modules/microshift-oc-mirror-install-catalog-cluster.adoc +++ b/modules/microshift-oc-mirror-install-catalog-cluster.adoc @@ -32,7 +32,7 @@ metadata: namespace: openshift-marketplace <1> spec: sourceType: grpc - image: registry.example.com/redhat/redhat-operator-index:v4.15 + image: registry.example.com/redhat/redhat-operator-index:v4.16 updateStrategy: registryPoll: interval: 60m diff --git a/modules/microshift-oc-mirror-list-ops-catalogs.adoc b/modules/microshift-oc-mirror-list-ops-catalogs.adoc index 1025dc5b53..f1ed5b8a4c 100644 --- a/modules/microshift-oc-mirror-list-ops-catalogs.adoc +++ b/modules/microshift-oc-mirror-list-ops-catalogs.adoc @@ -42,13 +42,13 @@ $ oc mirror list operators <--catalog=> <1> + [source,terminal] ---- -$ oc mirror list operators --catalog=registry.redhat.io/redhat/redhat-operator-index:v4.15 --package=amq-broker-rhel8 +$ oc mirror list operators --catalog=registry.redhat.io/redhat/redhat-operator-index:v4.16 --package=amq-broker-rhel8 ---- .. Get a list of versions within a channel by running the following command: + [source,terminal] ---- -$ oc mirror list operators --catalog=registry.redhat.io/redhat/redhat-operator-index:v4.15 --package=amq-broker-rhel8 --channel=7.11.x +$ oc mirror list operators --catalog=registry.redhat.io/redhat/redhat-operator-index:v4.16 --package=amq-broker-rhel8 --channel=7.11.x ---- .Next steps diff --git a/modules/microshift-ops-config-embed-ostree.adoc b/modules/microshift-ops-config-embed-ostree.adoc index 264405bd4a..c6fcc708f0 100644 --- a/modules/microshift-ops-config-embed-ostree.adoc +++ b/modules/microshift-ops-config-embed-ostree.adoc @@ -26,7 +26,7 @@ metadata: name: cs-redhat-operator-index namespace: openshift-marketplace <1> spec: - image: registry.example.com/redhat/redhat-operator-index:v4.15 + image: registry.example.com/redhat/redhat-operator-index:v4.16 sourceType: grpc displayName: publisher: diff --git a/modules/microshift-updating-rpms-y.adoc b/modules/microshift-updating-rpms-y.adoc index a43ae5b6c5..6f4093e8b3 100644 --- a/modules/microshift-updating-rpms-y.adoc +++ b/modules/microshift-updating-rpms-y.adoc @@ -6,11 +6,11 @@ [id="microshift-updating-rpms_{context}"] = Applying minor-version updates with RPMs -Updating a {microshift-short} minor version on non `rpm-ostree` systems such as {op-system-base-full} requires downloading then updating the RPMs. For example, use the following procedure to update from 4.14 to 4.15. +Updating a {microshift-short} minor version on non `rpm-ostree` systems such as {op-system-base-full} requires downloading then updating the RPMs. For example, use the following procedure to update from 4.15 to 4.16. [IMPORTANT] ==== -You can only update {microshift-short} from one version to the next in sequence. Jumping minor versions is not supported. For example, must update 4.14 to 4.15. +You can only update {microshift-short} from one version to the next in sequence. Jumping minor versions is not supported. For example, must update 4.15 to 4.16. ==== .Prerequisites diff --git a/modules/nw-ptp-e810-hardware-configuration-reference.adoc b/modules/nw-ptp-e810-hardware-configuration-reference.adoc index 7a46319ef5..8e86bfcefc 100644 --- a/modules/nw-ptp-e810-hardware-configuration-reference.adoc +++ b/modules/nw-ptp-e810-hardware-configuration-reference.adoc @@ -6,7 +6,7 @@ [id="nw-ptp-wpc-hardware-pins-reference_{context}"] = Intel Westport Channel E810 hardware configuration reference -Use this information to understand how to use the link:https://github.com/openshift/linuxptp-daemon/blob/release-4.15/addons/intel/e810.go[Intel E810-XXVDA4T hardware plugin] to configure the E810 network interface as PTP grandmaster clock. +Use this information to understand how to use the link:https://github.com/openshift/linuxptp-daemon/blob/release-4.16/addons/intel/e810.go[Intel E810-XXVDA4T hardware plugin] to configure the E810 network interface as PTP grandmaster clock. Hardware pin configuration determines how the network interface interacts with other components and devices in the system. The E810-XXVDA4T NIC has four connectors for external 1PPS signals: `SMA1`, `SMA2`, `U.FL1`, and `U.FL2`. diff --git a/modules/oadp-gcp-wif-cloud-authentication.adoc b/modules/oadp-gcp-wif-cloud-authentication.adoc index a3061fdfaa..dcdbb35e71 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.15/installing/installing_gcp/installing-gcp-customizations.html#installing-gcp-with-short-term-creds_installing-gcp-customizations[GCP Workload Identity configured]. +* You have installed a cluster in manual mode with link:https://docs.openshift.com/container-platform/4.16/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-imageset-config-params.adoc b/modules/oc-mirror-imageset-config-params.adoc index 6334254514..0808985dbd 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.15`. +|String. For example, `registry.redhat.io/redhat/redhat-operator-index:v4.16`. |`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.15`. +|String. For example, `fast` or `stable-v4.16`. |`mirror.operators.packages.channels.maxVersion` |The highest version of the Operator mirror across all channels in which it exists. See the note that follows the table for further information. @@ -243,7 +243,7 @@ channels: |`mirror.platform.channels.name` |The name of the release channel. -|String. For example, `stable-4.15` +|String. For example, `stable-4.16` |`mirror.platform.channels.minVersion` |The minimum version of the referenced platform to be mirrored. @@ -251,7 +251,7 @@ channels: |`mirror.platform.channels.maxVersion` |The highest version of the referenced platform to be mirrored. -|String. For example, `4.15.1` +|String. For example, `4.16.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 e08aa38514..fd47ade7d8 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.15/web_console/adding-user-preferences.html[Adding User Preferences] for more information on changing perspectives. +See link:https://docs.openshift.com/container-platform/4.16/web_console/adding-user-preferences.html[Adding User Preferences] for more information on changing perspectives. .Procedure diff --git a/modules/olm-catalogsource-image-template.adoc b/modules/olm-catalogsource-image-template.adoc index b8a897a929..cede83876b 100644 --- a/modules/olm-catalogsource-image-template.adoc +++ b/modules/olm-catalogsource-image-template.adoc @@ -14,18 +14,18 @@ endif::[] Operator compatibility with the underlying cluster can be expressed by a catalog source in various ways. One way, which is used for the default Red Hat-provided catalog sources, is to identify image tags for index images that are specifically created for a particular platform release, for example {product-title} {product-version}. -During a cluster upgrade, the index image tag for the default Red Hat-provided catalog sources are updated automatically by the Cluster Version Operator (CVO) so that Operator Lifecycle Manager (OLM) pulls the updated version of the catalog. For example during an upgrade from {product-title} 4.14 to 4.15, the `spec.image` field in the `CatalogSource` object for the `redhat-operators` catalog is updated from: +During a cluster upgrade, the index image tag for the default Red Hat-provided catalog sources are updated automatically by the Cluster Version Operator (CVO) so that Operator Lifecycle Manager (OLM) pulls the updated version of the catalog. For example during an upgrade from {product-title} 4.15 to 4.16, the `spec.image` field in the `CatalogSource` object for the `redhat-operators` catalog is updated from: [source,terminal] ---- -registry.redhat.io/redhat/redhat-operator-index:v4.14 +registry.redhat.io/redhat/redhat-operator-index:v4.15 ---- to: [source,terminal] ---- -registry.redhat.io/redhat/redhat-operator-index:v4.15 +registry.redhat.io/redhat/redhat-operator-index:v4.16 ---- However, the CVO does not automatically update image tags for custom catalogs. To ensure users are left with a compatible and supported Operator installation after a cluster upgrade, custom catalogs should also be kept updated to reference an updated index image. diff --git a/modules/olmv1-adding-a-catalog.adoc b/modules/olmv1-adding-a-catalog.adoc index 49e5377cec..f5f95c5360 100644 --- a/modules/olmv1-adding-a-catalog.adoc +++ b/modules/olmv1-adding-a-catalog.adoc @@ -99,7 +99,7 @@ Spec: Source: Image: Pull Secret: redhat-cred - Ref: registry.redhat.io/redhat/redhat-operator-index:v4.15 + Ref: registry.redhat.io/redhat/redhat-operator-index:v4.16 Type: image Status: <1> Conditions: @@ -114,7 +114,7 @@ Status: <1> Resolved Source: Image: Last Poll Attempt: 2024-01-10T16:18:51Z - Ref: registry.redhat.io/redhat/redhat-operator-index:v4.15 + Ref: registry.redhat.io/redhat/redhat-operator-index:v4.16 Resolved Ref: registry.redhat.io/redhat/redhat-operator-index@sha256:7b536ae19b8e9f74bb521c4a61e5818e036ac1865a932f2157c6c9a766b2eea5 <4> Type: image Events: diff --git a/modules/rosa-create-objects.adoc b/modules/rosa-create-objects.adoc index 09c1ca259f..9947cc7c0f 100644 --- a/modules/rosa-create-objects.adoc +++ b/modules/rosa-create-objects.adoc @@ -293,7 +293,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.15.0`. For `account-role` use an `X.Y` format, for example, `4.15`. +|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.16.0`. For `account-role` use an `X.Y` format, for example, `4.16`. |--worker-iam-role string |The ARN of the IAM role that will be attached to compute instances. diff --git a/modules/rosa-deleting-account-wide-iam-roles-and-policies.adoc b/modules/rosa-deleting-account-wide-iam-roles-and-policies.adoc index 0bf28b29a9..5075277302 100644 --- a/modules/rosa-deleting-account-wide-iam-roles-and-policies.adoc +++ b/modules/rosa-deleting-account-wide-iam-roles-and-policies.adoc @@ -75,9 +75,9 @@ ifdef::hcp[] ---- I: Fetching account roles ROLE NAME ROLE TYPE ROLE ARN OPENSHIFT VERSION AWS Managed -ManagedOpenShift-HCP-ROSA-Installer-Role Installer arn:aws:iam:::role/ManagedOpenShift-HCP-ROSA-Installer-Role 4.15 Yes -ManagedOpenShift-HCP-ROSA-Support-Role Support arn:aws:iam:::role/ManagedOpenShift-HCP-ROSA-Support-Role 4.15 Yes -ManagedOpenShift-HCP-ROSA-Worker-Role Worker arn:aws:iam:::role/ManagedOpenShift-HCP-ROSA-Worker-Role 4.15 Yes +ManagedOpenShift-HCP-ROSA-Installer-Role Installer arn:aws:iam:::role/ManagedOpenShift-HCP-ROSA-Installer-Role 4.16 Yes +ManagedOpenShift-HCP-ROSA-Support-Role Support arn:aws:iam:::role/ManagedOpenShift-HCP-ROSA-Support-Role 4.16 Yes +ManagedOpenShift-HCP-ROSA-Worker-Role Worker arn:aws:iam:::role/ManagedOpenShift-HCP-ROSA-Worker-Role 4.16 Yes ---- endif::hcp[] .. Delete the account-wide roles: diff --git a/modules/rosa-hcp-deleting-cluster.adoc b/modules/rosa-hcp-deleting-cluster.adoc index 511317999d..22d5b3d0d1 100644 --- a/modules/rosa-hcp-deleting-cluster.adoc +++ b/modules/rosa-hcp-deleting-cluster.adoc @@ -40,7 +40,7 @@ Display Name: test_cluster ID: <1> External ID: Control Plane: ROSA Service Hosted -OpenShift Version: 4.15.0 +OpenShift Version: 4.16.0 Channel Group: stable DNS: test_cluster.l3cn.p3.openshiftapps.com AWS Account: diff --git a/modules/rosa-hcp-sts-creating-a-cluster-external-auth-cluster-cli.adoc b/modules/rosa-hcp-sts-creating-a-cluster-external-auth-cluster-cli.adoc index 64241544c3..1005ae8f4b 100644 --- a/modules/rosa-hcp-sts-creating-a-cluster-external-auth-cluster-cli.adoc +++ b/modules/rosa-hcp-sts-creating-a-cluster-external-auth-cluster-cli.adoc @@ -56,7 +56,7 @@ Display Name: rosa-ext-test ID: External ID: Control Plane: ROSA Service Hosted -OpenShift Version: 4.15.3 +OpenShift Version: 4.16.3 Channel Group: stable DNS: AWS Account: diff --git a/modules/rosa-sts-account-wide-role-and-policy-commands.adoc b/modules/rosa-sts-account-wide-role-and-policy-commands.adoc index 222ac35911..1bd91e7057 100644 --- a/modules/rosa-sts-account-wide-role-and-policy-commands.adoc +++ b/modules/rosa-sts-account-wide-role-and-policy-commands.adoc @@ -11,7 +11,7 @@ This section lists the `aws` CLI commands that the `rosa` command generates in t [id="rosa-sts-account-wide-role-and-policy-aws-cli-manual-mode_{context}"] == Using manual mode for account role creation -The manual role creation mode generates the `aws` commands for you to review and run. The following command starts that process, where `` refers to your version of {product-title} (ROSA), such as `4.15`. +The manual role creation mode generates the `aws` commands for you to review and run. The following command starts that process, where `` refers to your version of {product-title} (ROSA), such as `4.16`. [source,terminal] ---- diff --git a/modules/rosa-sts-account-wide-roles-and-policies.adoc b/modules/rosa-sts-account-wide-roles-and-policies.adoc index 326fd2f88e..7732155b45 100644 --- a/modules/rosa-sts-account-wide-roles-and-policies.adoc +++ b/modules/rosa-sts-account-wide-roles-and-policies.adoc @@ -7,7 +7,7 @@ This section provides details about the account-wide IAM roles and policies that are required for ROSA deployments that use STS, including the Operator policies. It also includes the JSON files that define the policies. -The account-wide roles and policies are specific to an OpenShift minor release version, for example OpenShift 4.15, and are backward compatible. You can minimize the required STS resources by reusing the account-wide roles and policies for multiple clusters of the same minor version, regardless of their patch version. +The account-wide roles and policies are specific to an OpenShift minor release version, for example OpenShift 4.16, and are backward compatible. You can minimize the required STS resources by reusing the account-wide roles and policies for multiple clusters of the same minor version, regardless of their patch version. [id="rosa-sts-account-wide-roles-and-policies-creation-methods_{context}"] == Methods of account-wide role creation diff --git a/modules/rosa-sts-cluster-terraform-file-creation.adoc b/modules/rosa-sts-cluster-terraform-file-creation.adoc index a3e0be382c..b94fc342be 100644 --- a/modules/rosa-sts-cluster-terraform-file-creation.adoc +++ b/modules/rosa-sts-cluster-terraform-file-creation.adoc @@ -369,8 +369,8 @@ endif::tf-defaults[] $ cat<<-EOF>variables.tf variable "rosa_openshift_version" { type = string - default = "4.15.0" - description = "Desired version of OpenShift for the cluster, for example '4.15.0'. If version is greater than the currently running version, an upgrade will be scheduled." + default = "4.16.0" + description = "Desired version of OpenShift for the cluster, for example '4.16.0'. If version is greater than the currently running version, an upgrade will be scheduled." } variable "account_role_policies" { 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 5caaed0a91..274ca79399 100644 --- a/modules/rosa-sts-creating-a-cluster-with-customizations-cli.adoc +++ b/modules/rosa-sts-creating-a-cluster-with-customizations-cli.adoc @@ -224,7 +224,7 @@ Any optional fields can be left empty and a default will be selected. ? Create cluster admin user: Yes <2> ? Username: user-admin <2> ? Password: [? for help] *************** <2> -? OpenShift version: 4.15.0 <3> +? OpenShift version: 4.16.0 <3> ? Configure the use of IMDSv2 for ec2 instances optional/required (optional): <4> I: Using arn:aws:iam:::role/ManagedOpenShift-Installer-Role for the Installer role <5> I: Using arn:aws:iam:::role/ManagedOpenShift-ControlPlane-Role for the ControlPlane role @@ -254,7 +254,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.15.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 <14> + 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.16.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 <14> 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. @@ -262,7 +262,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 for your cluster. Selecting `Yes` then prompts you to create a user name and password for the cluster admin. The user name must not contain `/`, `:`, or `%`. The password must be at least 14 characters (ASCII-standard) without whitespaces. This process automatically configures an htpasswd identity provider. -<3> When creating the cluster, the listed `OpenShift version` options include the major, minor, and patch versions, for example `4.15.0`. +<3> When creating the cluster, the listed `OpenShift version` options include the major, minor, and patch versions, for example `4.16.0`. <4> 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. + [IMPORTANT] diff --git a/modules/rosa-sts-overview-of-the-default-cluster-specifications.adoc b/modules/rosa-sts-overview-of-the-default-cluster-specifications.adoc index 1ead46b34a..437ed75559 100644 --- a/modules/rosa-sts-overview-of-the-default-cluster-specifications.adoc +++ b/modules/rosa-sts-overview-of-the-default-cluster-specifications.adoc @@ -55,7 +55,7 @@ endif::rosa-terraform[] |Cluster settings | ifdef::rosa-terraform[] -* Default cluster version: `4.15.0` +* Default cluster version: `4.16.0` * Cluster name: `rosa-<6-digit-alphanumeric-string>` endif::rosa-terraform[] ifndef::rosa-terraform[] diff --git a/modules/sd-understanding-process-id-limits.adoc b/modules/sd-understanding-process-id-limits.adoc index 5123a87999..7870bed09d 100644 --- a/modules/sd-understanding-process-id-limits.adoc +++ b/modules/sd-understanding-process-id-limits.adoc @@ -14,7 +14,7 @@ The default value is 4,096 in {product-title} 4.11 and later. This value is cont * Maximum number of PIDs per node. + -The default value depends on link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.15/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.16/html-single/nodes/index#nodes-nodes-resources-configuring[node resources]. In {product-title}, this value is controlled by the link:https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/#system-reserved[`--system-reserved`] parameter, which reserves PIDs on each node based on the total resources of the node. When a pod exceeds the allowed maximum number of PIDs per pod, the pod might stop functioning correctly and might be evicted from the node. See link:https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals-and-thresholds[the Kubernetes documentation for eviction signals and thresholds] for more information. diff --git a/modules/serverless-quarkus-template.adoc b/modules/serverless-quarkus-template.adoc index 19947bb04a..8954843dea 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.15 + 4.16 test diff --git a/modules/telco-core-power-management.adoc b/modules/telco-core-power-management.adoc index 136b86879f..b0cec97db6 100644 --- a/modules/telco-core-power-management.adoc +++ b/modules/telco-core-power-management.adoc @@ -11,12 +11,12 @@ New in this release:: Description:: -The link:https://docs.openshift.com/container-platform/4.15/rest_api/node_apis/performanceprofile-performance-openshift-io-v2.html#spec-workloadhints[Performance Profile] can be used to configure a cluster in a high power, low power, or mixed mode. +The link:https://docs.openshift.com/container-platform/4.16/rest_api/node_apis/performanceprofile-performance-openshift-io-v2.html#spec-workloadhints[Performance Profile] can be used to configure a cluster in a high power, low power, or mixed mode. The choice of power mode depends on the characteristics of the workloads running on the cluster, particularly how sensitive they are to latency. Configure the maximum latency for a low-latency pod by using the per-pod power management C-states feature. + -For more information, see link:https://docs.openshift.com/container-platform/4.15/scalability_and_performance/low_latency_tuning/cnf-tuning-low-latency-nodes-with-perf-profile.html#cnf-configuring-power-saving-for-nodes_cnf-low-latency-perf-profile[Configuring power saving for nodes]. +For more information, see link:https://docs.openshift.com/container-platform/4.16/scalability_and_performance/low_latency_tuning/cnf-tuning-low-latency-nodes-with-perf-profile.html#cnf-configuring-power-saving-for-nodes_cnf-low-latency-perf-profile[Configuring power saving for nodes]. Limits and requirements:: * Power configuration relies on appropriate BIOS configuration, for example, enabling C-states and P-states. Configuration varies between hardware vendors. diff --git a/modules/telco-core-scheduling.adoc b/modules/telco-core-scheduling.adoc index 156e23c116..ecaef99dfe 100644 --- a/modules/telco-core-scheduling.adoc +++ b/modules/telco-core-scheduling.adoc @@ -12,12 +12,12 @@ New in this release:: Description:: * The scheduler is a cluster-wide component responsible for selecting the right node for a given workload. It is a core part of the platform and does not require any specific configuration in the common deployment scenarios. However, there are few specific use cases described in the following section. NUMA-aware scheduling can be enabled through the NUMA Resources Operator. -For more information, see link:https://docs.openshift.com/container-platform/4.15/scalability_and_performance/cnf-numa-aware-scheduling.html[Scheduling NUMA-aware workloads]. +For more information, see link:https://docs.openshift.com/container-platform/4.16/scalability_and_performance/cnf-numa-aware-scheduling.html[Scheduling NUMA-aware workloads]. Limits and requirements:: -* The default scheduler does not understand the NUMA locality of workloads. It only knows about the sum of all free resources on a worker node. This might cause workloads to be rejected when scheduled to a node with https://docs.openshift.com/container-platform/4.15/scalability_and_performance/using-cpu-manager.html#topology_manager_policies_using-cpu-manager-and-topology_manager[Topology manager policy] set to `single-numa-node` or `restricted`. +* The default scheduler does not understand the NUMA locality of workloads. It only knows about the sum of all free resources on a worker node. This might cause workloads to be rejected when scheduled to a node with https://docs.openshift.com/container-platform/4.16/scalability_and_performance/using-cpu-manager.html#topology_manager_policies_using-cpu-manager-and-topology_manager[Topology manager policy] set to `single-numa-node` or `restricted`. ** For example, consider a pod requesting 6 CPUs and being scheduled to an empty node that has 4 CPUs per NUMA node. The total allocatable capacity of the node is 8 CPUs and the scheduler will place the pod there. The node local admission will fail, however, as there are only 4 CPUs available in each of the NUMA nodes. -** All clusters with multi-NUMA nodes are required to use the https://docs.openshift.com/container-platform/4.15/scalability_and_performance/cnf-numa-aware-scheduling.html#installing-the-numa-resources-operator_numa-aware[NUMA Resources Operator]. The `machineConfigPoolSelector` of the NUMA Resources Operator must select all nodes where NUMA aligned scheduling is needed. +** All clusters with multi-NUMA nodes are required to use the https://docs.openshift.com/container-platform/4.16/scalability_and_performance/cnf-numa-aware-scheduling.html#installing-the-numa-resources-operator_numa-aware[NUMA Resources Operator]. The `machineConfigPoolSelector` of the NUMA Resources Operator must select all nodes where NUMA aligned scheduling is needed. * All machine config pools must have consistent hardware configuration for example all nodes are expected to have the same NUMA zone count. Engineering considerations:: diff --git a/modules/telco-core-sriov.adoc b/modules/telco-core-sriov.adoc index c3c78e53e0..aed4f1f68f 100644 --- a/modules/telco-core-sriov.adoc +++ b/modules/telco-core-sriov.adoc @@ -25,7 +25,7 @@ SR-IOV enables physical network interfaces (PFs) to be divided into multiple vir Limits and requirements:: -* The network interface controllers supported are listed in link:https://docs.openshift.com/container-platform/4.15/networking/hardware_networks/about-sriov.html#supported-devices_about-sriov[Supported devices] +* The network interface controllers supported are listed in link:https://docs.openshift.com/container-platform/4.16/networking/hardware_networks/about-sriov.html#supported-devices_about-sriov[Supported devices] * SR-IOV and IOMMU enablement in BIOS: The SR-IOV Network Operator automatically enables IOMMU on the kernel command line. * SR-IOV VFs do not receive link state updates from PF. If link down detection is needed, it must be done at the protocol level. * `MultiNetworkPolicy` CRs can be applied to `netdevice` networks only. diff --git a/modules/telco-core-whats-new-ref-design.adoc b/modules/telco-core-whats-new-ref-design.adoc index 4ffc2adab0..71c9512353 100644 --- a/modules/telco-core-whats-new-ref-design.adoc +++ b/modules/telco-core-whats-new-ref-design.adoc @@ -17,5 +17,5 @@ The following features that are included in {product-title} {product-version} an //CNF-5528 |Multi-network policy support for IPv6 Networks |You can now create multi-network policies for IPv6 networks. -For more information, see link:https://docs.openshift.com/container-platform/4.15/networking/multiple_networks/configuring-multi-network-policy.html#nw-multi-network-policy-ipv6-support_configuring-multi-network-policy[Supporting multi-network policies in IPv6 networks]. +For more information, see link:https://docs.openshift.com/container-platform/4.16/networking/multiple_networks/configuring-multi-network-policy.html#nw-multi-network-policy-ipv6-support_configuring-multi-network-policy[Supporting multi-network policies in IPv6 networks]. |==== diff --git a/modules/telco-ran-bios-tuning.adoc b/modules/telco-ran-bios-tuning.adoc index 3d6209522e..f85f86780e 100644 --- a/modules/telco-ran-bios-tuning.adoc +++ b/modules/telco-ran-bios-tuning.adoc @@ -11,7 +11,7 @@ New in this release:: Description:: Configure system level performance. -See link:https://docs.openshift.com/container-platform/4.15/scalability_and_performance/ztp_far_edge/ztp-reference-cluster-configuration-for-vdu.html#ztp-du-configuring-host-firmware-requirements_sno-configure-for-vdu[Configuring host firmware for low latency and high performance] for recommended settings. +See link:https://docs.openshift.com/container-platform/4.16/scalability_and_performance/ztp_far_edge/ztp-reference-cluster-configuration-for-vdu.html#ztp-du-configuring-host-firmware-requirements_sno-configure-for-vdu[Configuring host firmware for low latency and high performance] for recommended settings. + If Ironic inspection is enabled, the firmware setting values are available from the per-cluster `BareMetalHost` CR on the hub cluster. You enable Ironic inspection with a label in the `spec.clusters.nodes` field in the `SiteConfig` CR that you use to install the cluster. diff --git a/modules/telco-ran-node-tuning-operator.adoc b/modules/telco-ran-node-tuning-operator.adoc index 9dae6ee291..447446de37 100644 --- a/modules/telco-ran-node-tuning-operator.adoc +++ b/modules/telco-ran-node-tuning-operator.adoc @@ -10,7 +10,7 @@ New in this release:: * No reference design updates in this release Description:: -You tune the cluster performance by link:https://docs.openshift.com/container-platform/4.15/scalability_and_performance/cnf-create-performance-profiles.html[creating a performance profile]. +You tune the cluster performance by link:https://docs.openshift.com/container-platform/4.16/scalability_and_performance/cnf-create-performance-profiles.html[creating a performance profile]. Settings that you configure with a performance profile include: + * Selecting the realtime or non-realtime kernel. @@ -64,13 +64,13 @@ Variation must still meet the specified limits. * Hardware without IRQ affinity support impacts isolated CPUs. To ensure that pods with guaranteed whole CPU QoS have full use of the allocated CPU, all hardware in the server must support IRQ affinity. -For more information, see link:https://docs.openshift.com/container-platform/4.15/scalability_and_performance/cnf-low-latency-tuning.html#about_irq_affinity_setting_cnf-master[About support of IRQ affinity setting]. +For more information, see link:https://docs.openshift.com/container-platform/4.16/scalability_and_performance/cnf-low-latency-tuning.html#about_irq_affinity_setting_cnf-master[About support of IRQ affinity setting]. [NOTE] ==== In {product-title} {product-version}, any `PerformanceProfile` CR configured on the cluster causes the Node Tuning Operator to automatically set all cluster nodes to use cgroup v1. -For more information about cgroups, see link:https://docs.openshift.com/container-platform/4.15/nodes/clusters/nodes-cluster-cgroups-2.html#nodes-clusters-cgroups-2_nodes-cluster-cgroups-2[Configuring Linux cgroup]. +For more information about cgroups, see link:https://docs.openshift.com/container-platform/4.16/nodes/clusters/nodes-cluster-cgroups-2.html#nodes-clusters-cgroups-2_nodes-cluster-cgroups-2[Configuring Linux cgroup]. ==== :FeatureName: cgroup v1 diff --git a/modules/telco-ran-ptp-operator.adoc b/modules/telco-ran-ptp-operator.adoc index 8fc21ed321..14f8b1dbf2 100644 --- a/modules/telco-ran-ptp-operator.adoc +++ b/modules/telco-ran-ptp-operator.adoc @@ -10,7 +10,7 @@ New in this release:: * No reference design updates in this release Description:: -See link:https://docs.openshift.com/container-platform/4.15/scalability_and_performance/ztp_far_edge/ztp-reference-cluster-configuration-for-vdu.html#ztp-sno-du-configuring-ptp_sno-configure-for-vdu[PTP timing] for details of support and configuration of PTP in cluster nodes. +See link:https://docs.openshift.com/container-platform/4.16/scalability_and_performance/ztp_far_edge/ztp-reference-cluster-configuration-for-vdu.html#ztp-sno-du-configuring-ptp_sno-configure-for-vdu[PTP timing] for details of support and configuration of PTP in cluster nodes. The DU node can run in the following modes: + * As an ordinary clock (OC) synced to a grandmaster clock or boundary clock (T-BC) @@ -28,7 +28,7 @@ Highly available boundary clocks are not supported. + -- -Events and metrics for grandmaster clocks are a Tech Preview feature added in the 4.14 {rds} RDS. For more information see link:https://docs.openshift.com/container-platform/4.15/networking/ptp/using-ptp-events.html[Using the PTP hardware fast event notifications framework]. +Events and metrics for grandmaster clocks are a Tech Preview feature added in the 4.14 {rds} RDS. For more information see link:https://docs.openshift.com/container-platform/4.16/networking/ptp/using-ptp-events.html[Using the PTP hardware fast event notifications framework]. You can subscribe applications to PTP events that happen on the node where the DU application is running. -- diff --git a/modules/telco-ran-red-hat-advanced-cluster-management-rhacm.adoc b/modules/telco-ran-red-hat-advanced-cluster-management-rhacm.adoc index 1deeb5af4f..5ba7c6b1b0 100644 --- a/modules/telco-ran-red-hat-advanced-cluster-management-rhacm.adoc +++ b/modules/telco-ran-red-hat-advanced-cluster-management-rhacm.adoc @@ -31,4 +31,4 @@ You can significantly reduce the number of policies by using a single group poli These configurations should be managed using {rh-rhacm} policy hub-side templating with values pulled from `ConfigMap` CRs based on the cluster name. * To save CPU resources on managed clusters, policies that apply static configurations should be unbound from managed clusters after {ztp} installation of the cluster. -For more information, see link:https://docs.openshift.com/container-platform/4.15/storage/understanding-persistent-storage.html#releasing_understanding-persistent-storage[Release a persistent volume]. +For more information, see link:https://docs.openshift.com/container-platform/4.16/storage/understanding-persistent-storage.html#releasing_understanding-persistent-storage[Release a persistent volume]. diff --git a/modules/update-preparing-ack.adoc b/modules/update-preparing-ack.adoc index aafb14da8e..c3b09e5849 100644 --- a/modules/update-preparing-ack.adoc +++ b/modules/update-preparing-ack.adoc @@ -6,7 +6,7 @@ [id="update-preparing-ack_{context}"] = Providing the administrator acknowledgment -After you have evaluated your cluster for any removed APIs and have migrated any removed APIs, you can acknowledge that your cluster is ready to upgrade from {product-title} 4.14 to 4.15. +After you have evaluated your cluster for any removed APIs and have migrated any removed APIs, you can acknowledge that your cluster is ready to upgrade from {product-title} 4.15 to 4.16. [WARNING] ==== @@ -19,9 +19,9 @@ Be aware that all responsibility falls on the administrator to ensure that all u .Procedure -* Run the following command to acknowledge that you have completed the evaluation and your cluster is ready for the Kubernetes API removals in {product-title} 4.15: +* Run the following command to acknowledge that you have completed the evaluation and your cluster is ready for the Kubernetes API removals in {product-title} 4.16: + [source,terminal] ---- -$ oc -n openshift-config patch cm admin-acks --patch '{"data":{"ack-4.13-kube-1.27-api-removals-in-4.15":"true"}}' --type=merge +$ oc -n openshift-config patch cm admin-acks --patch '{"data":{"ack-4.13-kube-1.27-api-removals-in-4.16":"true"}}' --type=merge ---- diff --git a/modules/using-assisted-installer-oci-agent-iso.adoc b/modules/using-assisted-installer-oci-agent-iso.adoc index 975969bda7..7d0a8a3432 100644 --- a/modules/using-assisted-installer-oci-agent-iso.adoc +++ b/modules/using-assisted-installer-oci-agent-iso.adoc @@ -37,7 +37,7 @@ From the {oci} web console, you must create the following resources: |Specify the base domain of the cluster, such as `splat-oci.devcluster.openshift.com`. Provided you previously created a compartment on {oci}, you can get this information by going to *DNS management* -> *Zones* -> *List scope* and then selecting the parent compartment. Your base domain should show under the *Public zones* tab. |*OpenShift version* -| Specify `OpenShift 4.15` or a later version. +| Specify `OpenShift 4.16` or a later version. |*CPU architecture* | Specify `x86_64` or `Arm64`. diff --git a/modules/verifying-cluster-install-oci-agent-based.adoc b/modules/verifying-cluster-install-oci-agent-based.adoc index 6a24210cde..a92844d8d0 100644 --- a/modules/verifying-cluster-install-oci-agent-based.adoc +++ b/modules/verifying-cluster-install-oci-agent-based.adoc @@ -63,8 +63,8 @@ $ oc get co [source,terminal] ---- NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE -authentication 4.15.0-0 True False False 6m18s -baremetal 4.15.0-0 True False False 2m42s -network 4.15.0-0 True True False 5m58s Progressing: … +authentication 4.16.0-0 True False False 6m18s +baremetal 4.16.0-0 True False False 2m42s +network 4.16.0-0 True True False 5m58s Progressing: … … ---- diff --git a/modules/virt-checking-storage-configuration.adoc b/modules/virt-checking-storage-configuration.adoc index 7da31be3b8..7df1c13db5 100644 --- a/modules/virt-checking-storage-configuration.adoc +++ b/modules/virt-checking-storage-configuration.adoc @@ -166,11 +166,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.15.2 + status.result.cnvVersion: 4.16.2 status.result.defaultStorageClass: trident-nfs <5> status.result.goldenImagesNoDataSource: # <6> status.result.goldenImagesNotUpToDate: # <7> - status.result.ocpVersion: 4.15.0 + status.result.ocpVersion: 4.16.0 status.result.storageMissingVolumeSnapshotClass: status.result.storageProfilesWithEmptyClaimPropertySets: # <8> status.result.storageProfilesWithSpecClaimPropertySets: 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 4e68c0219b..acdccfad9f 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.15/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.15/html-single/storage/index#persistent-storage-csi[configuring CSI volumes] is recommended when working with a CSI Operator and driver. +Familiarity with link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.16/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.16/html-single/storage/index#persistent-storage-csi[configuring CSI volumes] is recommended when working with a CSI Operator and driver. After installing the AWS EFS CSI Driver Operator, {product-title} installs the AWS EFS CSI Operator and the AWS EFS CSI driver by default in the `openshift-cluster-csi-drivers` namespace. This allows the AWS EFS CSI Driver Operator to create CSI-provisioned PVs that mount to AWS EFS assets. @@ -87,5 +87,5 @@ include::modules/persistent-storage-csi-olm-operator-uninstall.adoc[leveloffset= [role="_additional-resources"] == Additional resources -* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.15/html-single/storage/index#persistent-storage-csi[Configuring CSI volumes] +* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.16/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 1f25cab6ce..a54a204a5a 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.15/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.15/html-single/storage/index#persistent-storage-csi[configuring CSI volumes] is recommended when working with a CSI Operator and driver. +Familiarity with link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.16/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.16/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.15/html-single/authentication_and_authorization/index#cco-ccoctl-configuring_cco-mode-sts[Configuring the Cloud Credential Operator utility] +* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.16/html-single/authentication_and_authorization/index#cco-ccoctl-configuring_cco-mode-sts[Configuring the Cloud Credential Operator utility] :StorageClass: AWS EFS :Provisioner: efs.csi.aws.com @@ -80,5 +80,5 @@ include::modules/persistent-storage-csi-olm-operator-uninstall.adoc[leveloffset= [role="_additional-resources"] == Additional resources -* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.15/html-single/storage/index#persistent-storage-csi[Configuring CSI volumes] +* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.16/html-single/storage/index#persistent-storage-csi[Configuring CSI volumes] diff --git a/telco_ref_design_specs/core/telco-core-ref-design-components.adoc b/telco_ref_design_specs/core/telco-core-ref-design-components.adoc index 6335416084..7e0a011b11 100644 --- a/telco_ref_design_specs/core/telco-core-ref-design-components.adoc +++ b/telco_ref_design_specs/core/telco-core-ref-design-components.adoc @@ -14,102 +14,102 @@ include::modules/telco-core-cpu-partitioning-performance-tune.adoc[leveloffset=+ [role="_additional-resources"] .Additional resources -* link:https://docs.openshift.com/container-platform/4.15/scalability_and_performance/low_latency_tuning/cnf-tuning-low-latency-nodes-with-perf-profile.html#cnf-cpu-infra-container_cnf-master[Tuning nodes for low latency with the performance profile] +* link:https://docs.openshift.com/container-platform/4.16/scalability_and_performance/low_latency_tuning/cnf-tuning-low-latency-nodes-with-perf-profile.html#cnf-cpu-infra-container_cnf-master[Tuning nodes for low latency with the performance profile] -* link:https://docs.openshift.com/container-platform/4.15/scalability_and_performance/ztp_far_edge/ztp-reference-cluster-configuration-for-vdu.html#ztp-du-configuring-host-firmware-requirements_sno-configure-for-vdu[Configuring host firmware for low latency and high performance] +* link:https://docs.openshift.com/container-platform/4.16/scalability_and_performance/ztp_far_edge/ztp-reference-cluster-configuration-for-vdu.html#ztp-du-configuring-host-firmware-requirements_sno-configure-for-vdu[Configuring host firmware for low latency and high performance] include::modules/telco-core-service-mesh.adoc[leveloffset=+1] [role="_additional-resources"] .Additional resources -* link:https://docs.openshift.com/container-platform/4.15/service_mesh/v2x/ossm-about.html[About OpenShift Service Mesh] +* link:https://docs.openshift.com/container-platform/4.16/service_mesh/v2x/ossm-about.html[About OpenShift Service Mesh] include::modules/telco-core-rds-networking.adoc[leveloffset=+1] [role="_additional-resources"] .Additional resources -* link:https://docs.openshift.com/container-platform/4.15/networking/understanding-networking.html[Understanding networking] +* link:https://docs.openshift.com/container-platform/4.16/networking/understanding-networking.html[Understanding networking] include::modules/telco-core-cluster-network-operator.adoc[leveloffset=+2] [role="_additional-resources"] .Additional resources -* link:https://docs.openshift.com/container-platform/4.15/networking/cluster-network-operator.html#nw-cluster-network-operator_cluster-network-operator[Cluster Network Operator] +* link:https://docs.openshift.com/container-platform/4.16/networking/cluster-network-operator.html#nw-cluster-network-operator_cluster-network-operator[Cluster Network Operator] include::modules/telco-core-load-balancer.adoc[leveloffset=+2] [role="_additional-resources"] .Additional resources -* link:https://docs.openshift.com/container-platform/4.15/networking/metallb/about-metallb.html[About MetalLB and the MetalLB Operator] +* link:https://docs.openshift.com/container-platform/4.16/networking/metallb/about-metallb.html[About MetalLB and the MetalLB Operator] include::modules/telco-core-sriov.adoc[leveloffset=+2] [role="_additional-resources"] .Additional resources -* link:https://docs.openshift.com/container-platform/4.15/networking/hardware_networks/about-sriov.html[About SR-IOV hardware networks] +* link:https://docs.openshift.com/container-platform/4.16/networking/hardware_networks/about-sriov.html[About SR-IOV hardware networks] include::modules/telco-nmstate-operator.adoc[leveloffset=+2] [role="_additional-resources"] .Additional resources -* link:https://docs.openshift.com/container-platform/4.15/networking/k8s_nmstate/k8s-nmstate-about-the-k8s-nmstate-operator.html[About the Kubernetes NMState Operator] +* link:https://docs.openshift.com/container-platform/4.16/networking/k8s_nmstate/k8s-nmstate-about-the-k8s-nmstate-operator.html[About the Kubernetes NMState Operator] include::modules/telco-core-logging.adoc[leveloffset=+1] [role="_additional-resources"] .Additional resources -* link:https://docs.openshift.com/container-platform/4.15/observability/logging/cluster-logging.html[About logging] +* link:https://docs.openshift.com/container-platform/4.16/observability/logging/cluster-logging.html[About logging] include::modules/telco-core-power-management.adoc[leveloffset=+1] [role="_additional-resources"] .Additional resources -* link:https://docs.openshift.com/container-platform/4.15/scalability_and_performance/low_latency_tuning/cnf-tuning-low-latency-nodes-with-perf-profile.html#cnf-configuring-power-saving-for-nodes_cnf-low-latency-perf-profile[Configuring power saving for nodes that run colocated high and low priority workloads] +* link:https://docs.openshift.com/container-platform/4.16/scalability_and_performance/low_latency_tuning/cnf-tuning-low-latency-nodes-with-perf-profile.html#cnf-configuring-power-saving-for-nodes_cnf-low-latency-perf-profile[Configuring power saving for nodes that run colocated high and low priority workloads] include::modules/telco-core-storage.adoc[leveloffset=+1] [role="_additional-resources"] .Additional resources -* link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.15[Product Documentation for Red Hat OpenShift Data Foundation] +* link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.16[Product Documentation for Red Hat OpenShift Data Foundation] include::modules/telco-core-monitoring.adoc[leveloffset=+1] [role="_additional-resources"] .Additional resources -* link:https://docs.openshift.com/container-platform/4.15/observability/monitoring/monitoring-overview.html#about-openshift-monitoring[About {product-version} monitoring] +* link:https://docs.openshift.com/container-platform/4.16/observability/monitoring/monitoring-overview.html#about-openshift-monitoring[About {product-version} monitoring] include::modules/telco-core-scheduling.adoc[leveloffset=+1] [role="_additional-resources"] .Additional resources -* link:https://docs.openshift.com/container-platform/4.15/nodes/scheduling/nodes-scheduler-about.html[Controlling pod placement using the scheduler] +* link:https://docs.openshift.com/container-platform/4.16/nodes/scheduling/nodes-scheduler-about.html[Controlling pod placement using the scheduler] -* link:https://docs.openshift.com/container-platform/4.15/scalability_and_performance/cnf-numa-aware-scheduling.html[Scheduling NUMA-aware workloads] +* link:https://docs.openshift.com/container-platform/4.16/scalability_and_performance/cnf-numa-aware-scheduling.html[Scheduling NUMA-aware workloads] include::modules/telco-core-installation.adoc[leveloffset=+1] [role="_additional-resources"] .Additional resources -* link:https://docs.openshift.com/container-platform/4.15/installing/installing_with_agent_based_installer/installing-with-agent-based-installer.html[Installing an {product-title} cluster with the Agent-based Installer] +* link:https://docs.openshift.com/container-platform/4.16/installing/installing_with_agent_based_installer/installing-with-agent-based-installer.html[Installing an {product-title} cluster with the Agent-based Installer] include::modules/telco-core-security.adoc[leveloffset=+1] [role="_additional-resources"] .Additional resources -* link:https://docs.openshift.com/container-platform/4.15/authentication/managing-security-context-constraints.html[Managing security context constraints] +* link:https://docs.openshift.com/container-platform/4.16/authentication/managing-security-context-constraints.html[Managing security context constraints] include::modules/telco-core-scalability.adoc[leveloffset=+1] @@ -121,7 +121,7 @@ include::modules/telco-core-rds-disconnected.adoc[leveloffset=+2] [role="_additional-resources"] .Additional resources -* link:https://docs.openshift.com/container-platform/4.15/updating/updating_a_cluster/updating_disconnected_cluster/index.html[About cluster updates in a disconnected environment] +* link:https://docs.openshift.com/container-platform/4.16/updating/updating_a_cluster/updating_disconnected_cluster/index.html[About cluster updates in a disconnected environment] include::modules/telco-core-kernel.adoc[leveloffset=+2] diff --git a/telco_ref_design_specs/ran/telco-ran-ref-du-components.adoc b/telco_ref_design_specs/ran/telco-ran-ref-du-components.adoc index e5e9c8197f..86d9afeed9 100644 --- a/telco_ref_design_specs/ran/telco-ran-ref-du-components.adoc +++ b/telco_ref_design_specs/ran/telco-ran-ref-du-components.adoc @@ -45,9 +45,9 @@ include::modules/telco-ran-gitops-operator-and-ztp-plugins.adoc[leveloffset=+2] [role="_additional-resources"] .Additional resources -* link:https://docs.openshift.com/container-platform/4.15/scalability_and_performance/ztp_far_edge/ztp-preparing-the-hub-cluster.html#ztp-preparing-the-ztp-git-repository-ver-ind_ztp-preparing-the-hub-cluster[Preparing the {ztp} site configuration repository for version independence] +* link:https://docs.openshift.com/container-platform/4.16/scalability_and_performance/ztp_far_edge/ztp-preparing-the-hub-cluster.html#ztp-preparing-the-ztp-git-repository-ver-ind_ztp-preparing-the-hub-cluster[Preparing the {ztp} site configuration repository for version independence] -* link:https://docs.openshift.com/container-platform/4.15/scalability_and_performance/ztp_far_edge/ztp-advanced-policy-config.html#ztp-adding-new-content-to-gitops-ztp_ztp-advanced-policy-config[Adding custom content to the {ztp} pipeline] +* link:https://docs.openshift.com/container-platform/4.16/scalability_and_performance/ztp_far_edge/ztp-advanced-policy-config.html#ztp-adding-new-content-to-gitops-ztp_ztp-advanced-policy-config[Adding custom content to the {ztp} pipeline] include::modules/telco-ran-agent-based-installer-abi.adoc[leveloffset=+2] diff --git a/telco_ref_design_specs/ran/telco-ran-ref-du-crs.adoc b/telco_ref_design_specs/ran/telco-ran-ref-du-crs.adoc index 1ca5d0e2cc..5807fa4dcc 100644 --- a/telco_ref_design_specs/ran/telco-ran-ref-du-crs.adoc +++ b/telco_ref_design_specs/ran/telco-ran-ref-du-crs.adoc @@ -14,7 +14,7 @@ CR fields you can change are annotated in the CR with YAML comments. [NOTE] ==== You can extract the complete set of RAN DU CRs from the `ztp-site-generate` container image. -See link:https://docs.openshift.com/container-platform/4.15/scalability_and_performance/ztp_far_edge/ztp-preparing-the-hub-cluster.html#ztp-preparing-the-ztp-git-repository_ztp-preparing-the-hub-cluster[Preparing the GitOps ZTP site configuration repository] for more information. +See link:https://docs.openshift.com/container-platform/4.16/scalability_and_performance/ztp_far_edge/ztp-preparing-the-hub-cluster.html#ztp-preparing-the-ztp-git-repository_ztp-preparing-the-hub-cluster[Preparing the GitOps ZTP site configuration repository] for more information. ==== include::modules/telco-ran-crs-day-2-operators.adoc[leveloffset=+1] diff --git a/virt/support/virt-collecting-virt-data.adoc b/virt/support/virt-collecting-virt-data.adoc index 7fa74d0be2..4bad7aa647 100644 --- a/virt/support/virt-collecting-virt-data.adoc +++ b/virt/support/virt-collecting-virt-data.adoc @@ -39,7 +39,7 @@ Collecting data about your environment minimizes the time required to analyze an // must-gather not supported for ROSA/OSD, per Dustin Row ifndef::openshift-rosa,openshift-dedicated[] . xref:../../support/gathering-cluster-data.adoc#support_gathering_data_gathering-cluster-data[Collect must-gather data for the cluster]. -. link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.15/html-single/troubleshooting_openshift_data_foundation/index#downloading-log-files-and-diagnostic-information_rhodf[Collect must-gather data for {rh-storage-first}], if necessary. +. link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.16/html-single/troubleshooting_openshift_data_foundation/index#downloading-log-files-and-diagnostic-information_rhodf[Collect must-gather data for {rh-storage-first}], if necessary. . xref:../../virt/support/virt-collecting-virt-data.adoc#virt-using-virt-must-gather_virt-collecting-virt-data[Collect must-gather data for {VirtProductName}]. . xref:../../observability/monitoring/managing-metrics.adoc#querying-metrics-for-all-projects-as-an-administrator_managing-metrics[Collect Prometheus metrics for the cluster]. endif::openshift-rosa,openshift-dedicated[]