Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OSDOCS11998 Docs for OCPSTRAT-1656 Updated boot images: Phase 3 (AWS GA) #85757

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

mburke5678
Copy link
Contributor

@mburke5678 mburke5678 commented Dec 3, 2024

https://issues.redhat.com/browse/OSDOCS-11998

Link to docs preview:
Updated boot images -- Removed as a Technology Preview feature for in 4th paragraph. Removed TP note. No other changes.

QE review:

  • QE has approved this change.

@mburke5678 mburke5678 added this to the Planned for 4.18 GA milestone Dec 3, 2024
@openshift-ci openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Dec 3, 2024
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Dec 3, 2024

🤖 Wed Dec 04 15:12:49 - Prow CI generated the docs preview:

https://85757--ocpdocs-pr.netlify.app/openshift-enterprise/latest/machine_configuration/mco-update-boot-images.html

@mburke5678
Copy link
Contributor Author

@djoshy PTAL. Again, I want to confirm that there are no functionality changes in this graduation to GA.

@@ -16,9 +16,9 @@ This process could cause the following issues:
* Certificate expiration issues
* Version skew issues

To avoid these issues, you can configure your cluster to update the boot image whenever you update your cluster. By modifying the `MachineConfiguration` object, you can enable this feature. Currently, the ability to update the boot image is available for only Google Cloud Platform (GCP) clusters and as a Technology Preview feature for Amazon Web Services (AWS) clusters. It is not supported for clusters managed by the {cluster-capi-operator}.
To avoid these issues, you can configure your cluster to update the boot image whenever you update your cluster. By modifying the `MachineConfiguration` object, you can enable this feature. Currently, the ability to update the boot image is available for only Google Cloud Platform (GCP) and Amazon Web Services (AWS) clusters and as a Technology Preview feature for VMware vSphere clusters. It is not supported for clusters managed by the {cluster-capi-operator}.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This feature is currently not in tech preview for vsphere, we are hoping to be able to land that as tech preview in 4.19. Mind linking me to where you found that it is in 4.18? That probably needs to be corrected.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@djoshy I think I saw that vSphere had slipped to 4.19 after I made this change. Neglected to fix it. Sorry!

Copy link

openshift-ci bot commented Dec 4, 2024

@mburke5678: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@mburke5678 mburke5678 changed the title OSDOCS11998 Docs for OCPSTRAT-1656 Updated boot images: Phase 3 (AWS GA, vspere TP) OSDOCS11998 Docs for OCPSTRAT-1656 Updated boot images: Phase 3 (AWS GA) Dec 4, 2024
@mburke5678 mburke5678 added the peer-review-needed Signifies that the peer review team needs to review this PR label Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch/enterprise-4.18 peer-review-needed Signifies that the peer review team needs to review this PR size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants