openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

[enterprise-4.17] OSDOCS 15615 Clarity on bootimage changes on AWS and GCP

Browse Source
This commit is contained in:
Michael Burke
2025-08-07 15:06:41 -04:00
parent f55117a5e3
commit a0715fc13b
2 changed files with 30 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
machine_configuration/mco-update-boot-images.adoc
View File

@@ -23,9 +23,14 @@ include::snippets/technology-preview.adoc[]
If you are not using the default user data secret, named `worker-user-data`, in your machine set, or you have modified the `worker-user-data` secret, you should not use managed boot image updates. This is because the Machine Config Operator (MCO) updates the machine set to use a managed version of the secret. By using the managed boot images feature, you are giving up the capability to customize the secret stored in the machine set object.
To view the current boot image used in your cluster, examine a machine set:
To view the current boot image used in your cluster, examine a machine set.
.Example machine set with the boot image reference
[NOTE]
====
The location and format of the boot image within the machine set differs, based on the platform. However, the boot image is always listed in the `spec.template.spec.providerSpec.` parameter.
====
.Example GCP machine set with the boot image reference
[source,yaml]
----
@@ -51,6 +56,28 @@ spec:
----
<1> This boot image is the same as the originally-installed {product-title} version, in this example {product-title} 4.12, regardless of the current version of the cluster. The way that the boot image is represented in the machine set depends on the platform, as the structure of the `providerSpec` field differs from platform to platform.
.Example AWS machine set with the boot image reference
[source,yaml]
----
apiVersion: machine.openshift.io/v1beta1
kind: MachineSet
metadata:
name: ci-ln-hmy310k-72292-5f87z-worker-a
namespace: openshift-machine-api
spec:
# ...
template:
# ...
spec:
# ...
providerSpec:
value:
ami:
id: ami-0e8fd9094e487d1ff
# ...
----
If you configure your cluster to update your boot images, the boot image referenced in your machine sets matches the current version of the cluster.
include::modules/mco-update-boot-images-configuring.adoc[leveloffset=+1]

2
modules/mco-update-boot-images-configuring.adoc
View File

@@ -146,4 +146,4 @@ spec:
image: projects/rhcos-cloud/global/images/<boot_image> <1>
# ...
----
<1> This boot image is the same as the current {product-title} version.
<1> This boot image is the same as the current {product-title} version. The location and format of the boot image within the machine set differs, based on the platform. However, the boot image is always listed in the `spec.template.spec.providerSpec.` parameter.