From 07fd1fd3741a2ece43b84b213f5ef0c9af44f19e Mon Sep 17 00:00:00 2001 From: Michael Burke Date: Thu, 19 Mar 2026 17:31:49 -0400 Subject: [PATCH 1/8] OSDOCS Document how to perform boot image updates on marketplace clusters --- .../mco-update-boot-images-manual.adoc | 2 + modules/mco-update-boot-images-aws.adoc | 279 ++++++++++++++++++ 2 files changed, 281 insertions(+) create mode 100644 modules/mco-update-boot-images-aws.adoc diff --git a/machine_configuration/mco-update-boot-images-manual.adoc b/machine_configuration/mco-update-boot-images-manual.adoc index 6277a056220b..952e2d71f2ae 100644 --- a/machine_configuration/mco-update-boot-images-manual.adoc +++ b/machine_configuration/mco-update-boot-images-manual.adoc @@ -14,6 +14,8 @@ For {product-title} platforms that do not support automatic boot image updating Red{nbsp}Hat does not support manually updating the boot image in control plane nodes. ==== +include::modules/mco-update-boot-images-aws.adoc[leveloffset=+2] + include::modules/mco-update-boot-images-ibm-cloud.adoc[leveloffset=+1] include::modules/mco-update-boot-images-nutanix.adoc[leveloffset=+1] diff --git a/modules/mco-update-boot-images-aws.adoc b/modules/mco-update-boot-images-aws.adoc new file mode 100644 index 000000000000..2282140facda --- /dev/null +++ b/modules/mco-update-boot-images-aws.adoc @@ -0,0 +1,279 @@ +// Module included in the following assemblies: +// +// * machine_configuration/mco-update-boot-images.adoc + +:_mod-docs-content-type: PROCEDURE +[id="mco-update-boot-images-aws_{context}"] += Manually updating the boot image on an {aws-short} cluster + +[role="_abstract"] +For an {aws-first} cluster, you can manually update the boot image for your cluster by configuring your machine sets to use the latest {product-title} image as the boot image to help ensure any new nodes can scale up properly. + +The following procedure, which includes steps to create environment variables that facilitate running the required commands, shows how to identify the correct Amazon Machine Image (AMI) to use as the new boot image to use and how to modify your compute machine sets to use that image. + +The process differs for clusters that use a standard {product-title} image and clusters that use a {aws-short} Marketplace image. The following procedure helps determine which type of image you use. + +.Prerequisites + +* You have completed the general boot image prerequisites as described in the "Prerequisites" section of the link:https://access.redhat.com/articles/7053165#prerequisites-2[{product-title} Boot Image Updates knowledgebase article]. + +* You have installed the {oc-first}. + +* You have installed the link:https://aws.amazon.com/cli/[{aws-short} CLI]. + +* You configured an AWS account to host the cluster. For information, see "Configuring an AWS account". + +* For a cluster that uses a standard image, you have downloaded the latest version of the {product-title} installation program, openshift-install, from the {cluster-manager-url} for a standard cluster. For more information, see "Obtaining the installation program." + +* For a cluster that uses a standard image, you have installed the link:https://stedolan.github.io/jq/[`jq`] program. + +.Procedure + +. Determine if your cluster uses a standard {product-title} image or an {aws-short} Marketplace image: + +.. Obtain the current {aws-short} region where the cluster is installed and set the value in an environment variable by running the following command: ++ +[source,terminal] +---- +$ export REGION=$(oc get infrastructure cluster -o jsonpath='{.status.platformStatus.aws.region}') +---- + +.. Obtain the current Amazon Machine Image (AMI) ID for your region and set the value in an environment variable by running the following command: ++ +[source,terminal] +---- +$ export CURRENT_AMI=$(oc get machineset -n openshift-machine-api -o jsonpath='{.items[0].spec.template.spec.providerSpec.value.ami.id}') +---- + +.. Obtain the product ID for your AMI and region and set the value in an environment variable by running the following command: ++ +[source,terminal] +---- +$ export PRODUCT_ID=$(aws ec2 describe-images --image-ids "$CURRENT_AMI" --region "$REGION" \ + --query 'Images[0].Name' --output text | \ + grep -oE '[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}') +---- ++ +`CURRENT_AMI` and `REGION` are environment variables you created in previous steps. + +.. Display the contents of the `PRODUCT_ID` environment variable by running the following command: ++ +[source,terminal] +---- +$ echo $PRODUCT_ID +---- ++ +* If the output for the `PRODUCT_ID` environment variable is empty, as shown in the following example, your cluster uses a standard {product-title} image. ++ +.Example with empty output +[source,terminal] +---- +$ echo $PRODUCT_ID + +$ +---- ++ +* If the output for the `PRODUCT_ID` environment variable is not empty, as shown in the following example, your cluster uses an {aws-short} Marketplace image. ++ +.Example with non-empty output +[source,terminal] +---- +$ echo $PRODUCT_ID + +$ +---- ++ +* If the command returns an error, and you are unable to determine your cluster variant, please reach out to Red Hat Support. If the Red Hat Support determines that your cluster uses an {aws-short} Marketplace image, use the following table below to set the `PRODUCT_ID` environment variable. ++ +[source,terminal] +---- +$ export PRODUCT_ID= +---- ++ +[cols="1,1",options="header"] +|=== +| Variant | Product ID +| link:https://aws.amazon.com/marketplace/procurement/?productId=59ead7de-2540-4653-a8b0-fa7926d5c845[{product-title} on x86 - NA]| `59ead7de-2540-4653-a8b0-fa7926d5c845` +| link:https://aws.amazon.com/marketplace/procurement?productId=963b36c3-de6f-48ed-b802-2b38b2a2cdeb[{oke} on x86 - NA]| `963b36c3-de6f-48ed-b802-2b38b2a2cdeb` +| link:https://aws.amazon.com/marketplace/procurement?productId=f5da01a6-d046-487c-9072-42fe53b1cad4[{opp} on x86 - NA]| `f5da01a6-d046-487c-9072-42fe53b1cad4` +| link:https://aws.amazon.com/marketplace/procurement?productId=abc249f8-7440-45f7-a4b1-c026baff64c1[{product-title} on ARM - NA]| `abc249f8-7440-45f7-a4b1-c026baff64c1` +| link:https://aws.amazon.com/marketplace/procurement?productId=d2d3ebcd-c1ca-43d8-bf0a-530433200f35[{oke} on ARM - NA]| `d2d3ebcd-c1ca-43d8-bf0a-530433200f35` +| link:https://aws.amazon.com/marketplace/procurement?productId=be6d3e94-c8dc-4a3e-9218-4b449b11f06f[{opp} on ARM - NA]| `be6d3e94-c8dc-4a3e-9218-4b449b11f06f` +| link:https://aws.amazon.com/marketplace/procurement?productId=962791c7-3ae5-46d1-ba62-c7a5ebac54fd[{product-title} on x86 - EU, ME and Africa]| `962791c7-3ae5-46d1-ba62-c7a5ebac54fd` +| link:https://aws.amazon.com/marketplace/procurement?productId=7026c8d7-392c-4010-b93c-f93f7bc5495f[{oke} on x86 - EU, ME and Africa]| `7026c8d7-392c-4010-b93c-f93f7bc5495f` +| link:https://aws.amazon.com/marketplace/procurement?productId=628c9df3-0254-4f91-bc1f-8619d1b8eaa8[{opp} on x86 - EU, ME and Africa]| `628c9df3-0254-4f91-bc1f-8619d1b8eaa8` +|=== + +. Determine the AMI for the new boot image by using one of the following steps, depending upon the type of images used in your cluster: + +* For a cluster that uses a standard {product-title} image, perform the following steps: ++ +.. Set an environment variable with your cluster architecture by running the following command: ++ +[source,terminal] +---- +$ export ARCH= +---- ++ +Replace `` with one of the following values: ++ +-- +* `aarch64` for the AArch64 or ARM64 architecture +* `ppc64le` for the {ibm-power-name} (ppc64le) architecture +* `s390x` for the {ibm-z-name} and {ibm-linuxone-name} (s390x) architecture +* `x86_64` for the x86_64 or AMD64 architecture +-- ++ +You can find the architecture as a label in any `MachineSet` object. ++ +.Example machine set with an architecture label +[source,terminal] +---- +apiVersion: machine.openshift.io/v1beta1 +kind: MachineSet +metadata: + annotations: + capacity.cluster-autoscaler.kubernetes.io/labels: kubernetes.io/arch=amd64 +# ... +---- + +.. Set an environment variable for the new boot image AMI by running the following command: ++ +[source,terminal] +---- +$ export AMI_ID=$(openshift-install coreos print-stream-json | jq -r ".architectures.\"${ARCH}\".images.aws.regions.\"${REGION}\".image") +---- ++ +`ARCH` and `REGION` are environment variables you created in previous steps. + +.. Optional: View the {op-system-first} version of the new boot image by running the following command: ++ +[source,terminal] +---- +$ openshift-install coreos print-stream-json | jq -r ".architectures.\"${ARCH}\".images.aws.regions.\"${REGION}\".release" +---- ++ +.Example output +[source,terminal] +---- +9.6.20251212-1 +---- ++ +Make note of the {op-system} version for later use. + +* For a cluster that uses a {aws-short} Marketplace image, perform the following steps: ++ +.. Obtain a list of valid AMI images by running the following command: ++ +[source,terminal] +---- +$ aws ec2 describe-images --region "${REGION}export PRODUCT_ID" --filters "Name=name,Values=*${PRODUCT_ID}*" \ + --query 'reverse(sort_by(Images, &CreationDate))[].[CreationDate,ImageId,Name]' --output table +---- ++ +`REGION` and `PRODUCT_ID` are environment variables you created in previous steps. ++ +This command returns the AMIs ordered by creation date, with the latest images first. The {op-system} version of each AMI is contained in the AMI name. Choose a version that meets the skew requirements. ++ +Make note of the {op-system-first} version for later use. + +.. Assign the selected AMI ID to an environment variable: ++ +[source,terminal] +---- +$ export AMI_ID= +---- + +. Update each of your compute machine sets to include the new boot image: + +.. Obtain the name of your machine sets for use in the following step by running the following command: ++ +[source,terminal] +---- +$ oc get machineset -n openshift-machine-api +---- ++ +.Example output +[source,terminal] +---- +NAME DESIRED CURRENT READY AVAILABLE AGE +rhhdrbk-b5564-4pcm9-worker-0 3 3 3 3 123m +ci-ln-xj96skb-72292-48nm5-worker-d 1 1 1 1 27m +---- + +.. Edit a machine set to update the `image` field in the `providerSpec` stanza to add your boot image by running the following command: ++ +[source,terminal] +---- +$ oc patch machineset -n openshift-machine-api --type merge -p '{"spec":{"template":{"spec":{"providerSpec":{"value":{"ami":{"id":"'${AMI_ID}'"}}}}}}}' +---- ++ +Replace `` with the name of your machine set. + +This step will need to be repeated for all MachineSets in your cluster. You may verify the AMI first, if desired. + +.Verification + +. Scale up a machine set to check that the new node is using the new boot image: + +.. Increase the machine set replicas by one to trigger a new machine by running the following command: ++ +[source,terminal] +---- +$ oc scale --replicas= machineset -n openshift-machine-api +---- +where: + +``:: Specifies the total number of replicas, including any existing replicas, that you want for this machine set. +``:: Specifies the name of the machine set to scale. + +.. Optional: View the status of the machine set as it provisions by running the following command: ++ +[source,terminal] +---- +$ oc get machines.machine.openshift.io -n openshift-machine-api -w +---- ++ +It can take several minutes for the machine set to achieve the `Running` state. + +.. Verify that the new node has been created and is in the `Ready` state by running the following command: ++ +[source,terminal] +---- +$ oc get nodes +---- + +. Verify that the new node is using the new boot image by running the following command: ++ +[source,terminal] +---- +$ oc debug node/ -- chroot /host cat /sysroot/.coreos-aleph-version.json +---- ++ +Replace `` with the name of your new node. ++ +.Example output +[source,terminal] +---- +{ +# ... + "ref": "docker://ostree-image-signed:oci-archive:/rhcos-9.6.20251212-1-ostree.x86_64.ociarchive", + "version": "9.6.20251212-1" +} +---- +where: + +`version`:: Specifies the boot image version. + +. Verify that the boot image is the same the {op-system} version as the image you noted in a previous step by running the following command: ++ +[source,terminal] +---- +$ echo ${RHCOS_URL} +---- ++ +.Example output +[source,terminal] +---- +https://rhcos.mirror.openshift.com/art/storage/prod/streams/rhel-9.6/builds/9.6.20251212-1/x86_64/rhcos-9.6.20251212-1-nutanix.x86_64.qcow2 +---- From ee5772ec2d5a63a43621d05b90b8ab328a32fad7 Mon Sep 17 00:00:00 2001 From: Michael Burke Date: Fri, 20 Mar 2026 10:35:24 -0400 Subject: [PATCH 2/8] proofread --- modules/mco-update-boot-images-aws.adoc | 30 ++++++++++++------------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/modules/mco-update-boot-images-aws.adoc b/modules/mco-update-boot-images-aws.adoc index 2282140facda..5b1505d9af05 100644 --- a/modules/mco-update-boot-images-aws.adoc +++ b/modules/mco-update-boot-images-aws.adoc @@ -7,11 +7,11 @@ = Manually updating the boot image on an {aws-short} cluster [role="_abstract"] -For an {aws-first} cluster, you can manually update the boot image for your cluster by configuring your machine sets to use the latest {product-title} image as the boot image to help ensure any new nodes can scale up properly. +You can manually update the boot image for your {aws-first} cluster by configuring your machine sets to use the latest {product-title} image as the boot image to ensure that new nodes can scale up properly. -The following procedure, which includes steps to create environment variables that facilitate running the required commands, shows how to identify the correct Amazon Machine Image (AMI) to use as the new boot image to use and how to modify your compute machine sets to use that image. +The following procedure, which includes steps to create environment variables that facilitate running the required commands, shows how to identify the correct Amazon Machine Image (AMI) to use as the new boot image and how to modify your compute machine sets to use that image. -The process differs for clusters that use a standard {product-title} image and clusters that use a {aws-short} Marketplace image. The following procedure helps determine which type of image you use. +The process differs for clusters that use a default {op-system-first} image and clusters that use a custom {op-system-first} image from the {aws-short} Marketplace. The following procedure helps determine which type of image you use. .Prerequisites @@ -23,13 +23,13 @@ The process differs for clusters that use a standard {product-title} image and c * You configured an AWS account to host the cluster. For information, see "Configuring an AWS account". -* For a cluster that uses a standard image, you have downloaded the latest version of the {product-title} installation program, openshift-install, from the {cluster-manager-url} for a standard cluster. For more information, see "Obtaining the installation program." +* For a cluster that uses a default {op-system} image, you have downloaded the latest version of the {product-title} installation program, openshift-install, from the {cluster-manager-url}. For more information, see "Obtaining the installation program." -* For a cluster that uses a standard image, you have installed the link:https://stedolan.github.io/jq/[`jq`] program. +* For a cluster that uses a default {op-system} image, you have installed the link:https://stedolan.github.io/jq/[`jq`] program. .Procedure -. Determine if your cluster uses a standard {product-title} image or an {aws-short} Marketplace image: +. Determine if your cluster uses a default {op-system} image or a custom {op-system} image from the {aws-short} Marketplace image: .. Obtain the current {aws-short} region where the cluster is installed and set the value in an environment variable by running the following command: + @@ -45,7 +45,7 @@ $ export REGION=$(oc get infrastructure cluster -o jsonpath='{.status.platformSt $ export CURRENT_AMI=$(oc get machineset -n openshift-machine-api -o jsonpath='{.items[0].spec.template.spec.providerSpec.value.ami.id}') ---- -.. Obtain the product ID for your AMI and region and set the value in an environment variable by running the following command: +.. Obtain the product ID for your AMI and set the value in an environment variable by running the following command: + [source,terminal] ---- @@ -83,7 +83,7 @@ $ echo $PRODUCT_ID $ ---- + -* If the command returns an error, and you are unable to determine your cluster variant, please reach out to Red Hat Support. If the Red Hat Support determines that your cluster uses an {aws-short} Marketplace image, use the following table below to set the `PRODUCT_ID` environment variable. +* If the command returns an error, and you are unable to determine your cluster variant, contact Red Hat Support. If Red Hat Support determines that your cluster uses an {aws-short} Marketplace image, you can set the `PRODUCT_ID` environment variable with the appropriate product ID from the following table. + [source,terminal] ---- @@ -106,7 +106,7 @@ $ export PRODUCT_ID= . Determine the AMI for the new boot image by using one of the following steps, depending upon the type of images used in your cluster: -* For a cluster that uses a standard {product-title} image, perform the following steps: +* For a cluster that uses a default {op-system} image, perform the following steps: + .. Set an environment variable with your cluster architecture by running the following command: + @@ -137,7 +137,7 @@ metadata: # ... ---- -.. Set an environment variable for the new boot image AMI by running the following command: +.. Set an environment variable with the new boot image AMI by running the following command: + [source,terminal] ---- @@ -146,7 +146,7 @@ $ export AMI_ID=$(openshift-install coreos print-stream-json | jq -r ".architect + `ARCH` and `REGION` are environment variables you created in previous steps. -.. Optional: View the {op-system-first} version of the new boot image by running the following command: +.. View the {op-system-first} version of the new boot image by running the following command: + [source,terminal] ---- @@ -161,7 +161,7 @@ $ openshift-install coreos print-stream-json | jq -r ".architectures.\"${ARCH}\" + Make note of the {op-system} version for later use. -* For a cluster that uses a {aws-short} Marketplace image, perform the following steps: +* For a cluster that uses a custom {op-system} image, perform the following steps: + .. Obtain a list of valid AMI images by running the following command: + @@ -173,11 +173,11 @@ $ aws ec2 describe-images --region "${REGION}export PRODUCT_ID" --filters "Name= + `REGION` and `PRODUCT_ID` are environment variables you created in previous steps. + -This command returns the AMIs ordered by creation date, with the latest images first. The {op-system} version of each AMI is contained in the AMI name. Choose a version that meets the skew requirements. +This command returns the AMIs ordered by creation date, with the latest images first. The {op-system} version of each AMI is contained in the AMI name. Choose the latest image version available. + Make note of the {op-system-first} version for later use. -.. Assign the selected AMI ID to an environment variable: +.. Set an environment variable with the new boot image AMI by running the following command: + [source,terminal] ---- @@ -210,7 +210,7 @@ $ oc patch machineset -n openshift-machine-api --type merge -p + Replace `` with the name of your machine set. -This step will need to be repeated for all MachineSets in your cluster. You may verify the AMI first, if desired. +. If boot image skew enforcement is set to manual in your cluster, update the boot image version in the `MachineConfiguration` object as described in "Updating the boot image skew enforcement version." .Verification From 0cd711ff91393338b89a98c6131ea4a1c94dd80e Mon Sep 17 00:00:00 2001 From: Michael Burke Date: Fri, 20 Mar 2026 11:02:20 -0400 Subject: [PATCH 3/8] proofread --- modules/mco-update-boot-images-aws.adoc | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/modules/mco-update-boot-images-aws.adoc b/modules/mco-update-boot-images-aws.adoc index 5b1505d9af05..cd2b27010edd 100644 --- a/modules/mco-update-boot-images-aws.adoc +++ b/modules/mco-update-boot-images-aws.adoc @@ -118,10 +118,10 @@ $ export ARCH= Replace `` with one of the following values: + -- -* `aarch64` for the AArch64 or ARM64 architecture -* `ppc64le` for the {ibm-power-name} (ppc64le) architecture -* `s390x` for the {ibm-z-name} and {ibm-linuxone-name} (s390x) architecture -* `x86_64` for the x86_64 or AMD64 architecture +* Specify `aarch64` for the AArch64 or ARM64 architecture. +* Specify `ppc64le` for the {ibm-power-name} (ppc64le) architecture. +* Specify `s390x` for the {ibm-z-name} and {ibm-linuxone-name} (s390x) architecture. +* Specify `x86_64` for the x86_64 or AMD64 architecture. -- + You can find the architecture as a label in any `MachineSet` object. @@ -137,7 +137,7 @@ metadata: # ... ---- -.. Set an environment variable with the new boot image AMI by running the following command: +.. Set an environment variable with the AMI of the new boot image by running the following command: + [source,terminal] ---- @@ -177,7 +177,7 @@ This command returns the AMIs ordered by creation date, with the latest images f + Make note of the {op-system-first} version for later use. -.. Set an environment variable with the new boot image AMI by running the following command: +.. Set an environment variable with the AMI of the new boot image by running the following command: + [source,terminal] ---- @@ -209,8 +209,10 @@ $ oc patch machineset -n openshift-machine-api --type merge -p ---- + Replace `` with the name of your machine set. ++ +`AMI_ID` is the environment variable you created in a previous step. -. If boot image skew enforcement is set to manual in your cluster, update the boot image version in the `MachineConfiguration` object as described in "Updating the boot image skew enforcement version." +. If boot image skew enforcement in your cluster is set to the manual mode, update the boot image version in the `MachineConfiguration` object as described in "Updating the boot image skew enforcement version." .Verification @@ -272,6 +274,8 @@ where: $ echo ${RHCOS_URL} ---- + +`RHCOS_URL` is the environment variable you created in a previous step. ++ .Example output [source,terminal] ---- From f5d39a5742c3d51de863d677938ff91c9e7ad3bd Mon Sep 17 00:00:00 2001 From: Michael Burke Date: Fri, 20 Mar 2026 11:45:49 -0400 Subject: [PATCH 4/8] Add note on auto update --- modules/mco-update-boot-images-aws.adoc | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/modules/mco-update-boot-images-aws.adoc b/modules/mco-update-boot-images-aws.adoc index cd2b27010edd..14fa4ff60310 100644 --- a/modules/mco-update-boot-images-aws.adoc +++ b/modules/mco-update-boot-images-aws.adoc @@ -13,6 +13,11 @@ The following procedure, which includes steps to create environment variables th The process differs for clusters that use a default {op-system-first} image and clusters that use a custom {op-system-first} image from the {aws-short} Marketplace. The following procedure helps determine which type of image you use. +[NOTE] +==== +For clusters that use a default {op-system-first} image, you can configure the cluster to automatically update the boot image each time the cluster is updated. For more information, see "Boot image management". +==== + .Prerequisites * You have completed the general boot image prerequisites as described in the "Prerequisites" section of the link:https://access.redhat.com/articles/7053165#prerequisites-2[{product-title} Boot Image Updates knowledgebase article]. @@ -79,7 +84,7 @@ $ [source,terminal] ---- $ echo $PRODUCT_ID - +59ead7de-2540-4653-a8b0-fa7926d5c845 $ ---- + From 526f36f0bd7ee0062228bba27881c3160e2373f0 Mon Sep 17 00:00:00 2001 From: Michael Burke Date: Fri, 20 Mar 2026 14:04:06 -0400 Subject: [PATCH 5/8] edits per djoshy --- modules/mco-update-boot-images-aws.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/mco-update-boot-images-aws.adoc b/modules/mco-update-boot-images-aws.adoc index 14fa4ff60310..46017dea5f42 100644 --- a/modules/mco-update-boot-images-aws.adoc +++ b/modules/mco-update-boot-images-aws.adoc @@ -15,7 +15,7 @@ The process differs for clusters that use a default {op-system-first} image and [NOTE] ==== -For clusters that use a default {op-system-first} image, you can configure the cluster to automatically update the boot image each time the cluster is updated. For more information, see "Boot image management". +For clusters that use a default {op-system-first} image, you can configure the cluster to automatically update the boot image each time the cluster is updated. If you are using the following procedure, ensure that automatic boot image updates are disabled and skew enforcement is in manual mode. For more information, see "Boot image management" and "Boot image skew enforcement". ==== .Prerequisites From d7babf174e0419ebab6db80ab60d04f72e6b2db7 Mon Sep 17 00:00:00 2001 From: Michael Burke Date: Tue, 24 Mar 2026 15:56:30 -0400 Subject: [PATCH 6/8] edit --- modules/mco-update-boot-images-aws.adoc | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/modules/mco-update-boot-images-aws.adoc b/modules/mco-update-boot-images-aws.adoc index 46017dea5f42..c19cba6b852b 100644 --- a/modules/mco-update-boot-images-aws.adoc +++ b/modules/mco-update-boot-images-aws.adoc @@ -24,6 +24,10 @@ For clusters that use a default {op-system-first} image, you can configure the c * You have installed the {oc-first}. +* You have set boot image management to the manual or none mode. For more information, see "Configuring boot image skew enforcement". + +* You have disabled boot image management for the cluster. For more information, see "Disabling boot image management". + * You have installed the link:https://aws.amazon.com/cli/[{aws-short} CLI]. * You configured an AWS account to host the cluster. For information, see "Configuring an AWS account". From 09432453c8118ae92bd041802dff46d48bda9388 Mon Sep 17 00:00:00 2001 From: Michael Burke Date: Thu, 26 Mar 2026 18:03:09 -0400 Subject: [PATCH 7/8] proofread --- modules/mco-update-boot-images-aws.adoc | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/modules/mco-update-boot-images-aws.adoc b/modules/mco-update-boot-images-aws.adoc index c19cba6b852b..56b89a348cb8 100644 --- a/modules/mco-update-boot-images-aws.adoc +++ b/modules/mco-update-boot-images-aws.adoc @@ -24,7 +24,7 @@ For clusters that use a default {op-system-first} image, you can configure the c * You have installed the {oc-first}. -* You have set boot image management to the manual or none mode. For more information, see "Configuring boot image skew enforcement". +* You have set boot image skew enforcement to the manual or none mode. For more information, see "Configuring boot image skew enforcement". * You have disabled boot image management for the cluster. For more information, see "Disabling boot image management". @@ -146,7 +146,7 @@ metadata: # ... ---- -.. Set an environment variable with the AMI of the new boot image by running the following command: +.. Obtain the AMI for the new boot image and set an environment variable with the AMI by running the following command: + [source,terminal] ---- @@ -176,7 +176,7 @@ Make note of the {op-system} version for later use. + [source,terminal] ---- -$ aws ec2 describe-images --region "${REGION}export PRODUCT_ID" --filters "Name=name,Values=*${PRODUCT_ID}*" \ +$ aws ec2 describe-images --region "${REGION}" --filters "Name=name,Values=*${PRODUCT_ID}*" \ --query 'reverse(sort_by(Images, &CreationDate))[].[CreationDate,ImageId,Name]' --output table ---- + @@ -280,13 +280,13 @@ where: + [source,terminal] ---- -$ echo ${RHCOS_URL} +$ echo ${AMI_ID} ---- + -`RHCOS_URL` is the environment variable you created in a previous step. +`AMI_ID` is the environment variable you created in a previous step. + .Example output [source,terminal] ---- -https://rhcos.mirror.openshift.com/art/storage/prod/streams/rhel-9.6/builds/9.6.20251212-1/x86_64/rhcos-9.6.20251212-1-nutanix.x86_64.qcow2 +9.6.20251212-1 ---- From 50ba7b1690eb45edae96475487ef073001ed09a9 Mon Sep 17 00:00:00 2001 From: Michael Burke Date: Tue, 31 Mar 2026 16:10:14 -0400 Subject: [PATCH 8/8] Added Manually updating the boot image assembly --- machine_configuration/mco-update-boot-images-manual.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/machine_configuration/mco-update-boot-images-manual.adoc b/machine_configuration/mco-update-boot-images-manual.adoc index 952e2d71f2ae..61e07fbacf9d 100644 --- a/machine_configuration/mco-update-boot-images-manual.adoc +++ b/machine_configuration/mco-update-boot-images-manual.adoc @@ -14,7 +14,7 @@ For {product-title} platforms that do not support automatic boot image updating Red{nbsp}Hat does not support manually updating the boot image in control plane nodes. ==== -include::modules/mco-update-boot-images-aws.adoc[leveloffset=+2] +include::modules/mco-update-boot-images-aws.adoc[leveloffset=+1] include::modules/mco-update-boot-images-ibm-cloud.adoc[leveloffset=+1]