OSDOCS 15615 Clarity on bootimage changes on AWS and GCP#97038
OSDOCS 15615 Clarity on bootimage changes on AWS and GCP#97038dfitzmau merged 1 commit intoopenshift:mainfrom
Conversation
| ==== | ||
|
|
||
| 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. 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. |
There was a problem hiding this comment.
I wonder if we can put this in one of those fancy "warning" boxes? So it is a bit more easy to notice than a regular paragraph. Content sounds good to me!
|
@ptalgulk01 Can you PTAL? |
|
looks good |
|
/lgtm from MCO POV! |
835b836 to
7faca38
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. |
| .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. |
There was a problem hiding this comment.
| 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. | |
| 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. |
Visually might look better. If this is possible? Maybe a follow-up PR if the change is valid. I won't hold up PR merging.
|
/cherrypick enterprise-4.20 |
|
/cherrypick enterprise-4.19 |
|
/cherrypick enterprise-4.18 |
|
/cherrypick enterprise-4.17 |
|
@dfitzmau: #97038 failed to apply on top of branch "enterprise-4.18": 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. |
|
@dfitzmau: #97038 failed to apply on top of branch "enterprise-4.17": 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. |
|
@dfitzmau: new pull request created: #97314 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. |
|
@dfitzmau: new pull request created: #97315 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. |
https://issues.redhat.com/browse/OSDOCS-15615
Link to docs preview:
About boot image management -- New note; new AWS machine set example.
No QE review needed of the following changes:
Enabling boot image management -- Moved verification bullet 2 to snippet.
Disabling boot image management -- Moved verification bullet 2 to snippet.
QE review: