OSDOCS Document how to perform boot image updates on marketplace clusters AWS#108736
Conversation
|
🤖 Fri May 08 13:38:34 - Prow CI generated the docs preview: |
4a5fec7 to
0378257
Compare
|
@djoshy PTAL |
|
@ptalgulk01 @sergiordlr PTAL |
7e31627 to
50ba7b1
Compare
|
@HarshwardhanPatil07 PTAL |
| @@ -0,0 +1,292 @@ | |||
| // Module included in the following assemblies: | |||
| // | |||
| // * machine_configuration/mco-update-boot-images.adoc | |||
There was a problem hiding this comment.
Should be: // * machine_configuration/mco-update-boot-images-manual.adoc
| // * machine_configuration/mco-update-boot-images.adoc | |
| // * machine_configuration/mco-update-boot-images-manual.adoc |
|
|
||
| * 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". |
There was a problem hiding this comment.
can we add the link here for "Configuring an AWS account"?
| * You configured an AWS account to host the cluster. For information, see "Configuring an AWS account". | |
| * You configured an AWS account to host the cluster. For more information, see "Configuring an AWS account". |
There was a problem hiding this comment.
Unfortunately, due to the structure of our docs, we cannot add links to documents at the module/ level, only the assembly/ level.
| .Example output | ||
| [source,terminal] | ||
| ---- | ||
| 9.6.20251212-1 |
There was a problem hiding this comment.
I think AMI_ID format is different, can you please check it ones
There was a problem hiding this comment.
You seem to be correct. I am going to remove this step, as I don't think it adds anything based on the correct output of the command. Good catch!
There was a problem hiding this comment.
Thank you for looking into it. I did some stuff with AWS few months back and i just noticed it.
710c60a to
ba4ef2a
Compare
|
|
||
| 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 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. |
There was a problem hiding this comment.
| 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. | |
| The process differs for clusters that use a default {op-system-first} image and clusters that use a custom {op-system} 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. 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". |
There was a problem hiding this comment.
| 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". | |
| For clusters that use a default {op-system} 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". |
ba4ef2a to
c9bda29
Compare
|
New changes are detected. LGTM label has been removed. |
c9bda29 to
25dce91
Compare
25dce91 to
aa4a172
Compare
|
@mburke5678: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/cherrypick enterprise-4.22 |
|
@mburke5678: new pull request created: #111439 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Incorporate https://gist.github.com/djoshy/d7129328cd186471a5c0965b2bddd408
https://redhat.atlassian.net/browse/OSDOCS-18794
Link to docs preview:
Manually updating the boot image on an AWS cluster -- New module. Final location TBD.
Reviewer: The "Updating the boot image skew enforcement version" module is not available yet. Will add link later.
QE review: