-
Notifications
You must be signed in to change notification settings - Fork 1.9k
machine_management: add note about using original boot media #26215
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
Conversation
|
This should be added to the 4.6 docs, too |
yuqi-zhang
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that this isn't just 4.6, we've technically never "supported" updating boot media directly in any way. It just so happens that the 4.6 ignition spec upgrade is the first time we've updated the pointer config
Maybe worth being extra clear then and just saying to use the original boot media wiht no 4.6 caveat |
3d20207 to
eea640b
Compare
Pushed an update that was more clear |
kalexand-rh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have a few requests, but this is looking good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| When adding additional compute machines to your {product-title} cluster, you should use the | |
| When adding additional compute machines to your {product-title} cluster, use the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| {op-system} boot media that matches the same minor version that was used to originally | |
| {op-system} boot media that matches the same minor version that was used to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| install the {product-title} cluster. For example, if you originally installed | |
| install the {product-title} cluster. For example, if you installed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| {product-title} 4.4, you should add additional compute machines using {op-system} 4.4 | |
| {product-title} 4.4, you must add additional compute machines using {op-system} 4.4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a sentence about upgrading the machines after you add them.
bobfuru
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a suggestion to Kathryn's. Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding additional compute machines to your cluster using newer {op-system} boot media is not supported.
| It is not supported to add additional compute machines to your cluster using newer | |
| It is not supported to add additional compute machines to your cluster using newer |
machine_management/user_infra/adding-vsphere-compute-user-infra.adoc
Outdated
Show resolved
Hide resolved
We don't support using newer boot media to add nodes to a clusters.
eea640b to
d39a556
Compare
|
Thanks @kalexand-rh @bobfuru; pushed update with your feedback |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @miabbott - a minor nit that I missed before, use a single space between sentences. I'll go ahead and make the change. Otherwise, LGTM.
Let me know if you feel this is ready for me to squash and merge. Thanks!
machine_management/user_infra/adding-bare-metal-compute-user-infra.adoc
Outdated
Show resolved
Hide resolved
machine_management/user_infra/adding-bare-metal-compute-user-infra.adoc
Outdated
Show resolved
Hide resolved
machine_management/user_infra/adding-vsphere-compute-user-infra.adoc
Outdated
Show resolved
Hide resolved
machine_management/user_infra/adding-vsphere-compute-user-infra.adoc
Outdated
Show resolved
Hide resolved
|
@bobfuru The content looks good to me; ready for squash and merge |
|
/cherrypick enterprise-4.6 |
|
@bobfuru: new pull request created: #26359 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/test-infra repository. |
|
/cherrypick enterprise-4.5 |
|
/cherrypick enterprise-4.4 |
|
@bobfuru: new pull request created: #26361 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/test-infra repository. |
|
@bobfuru: new pull request created: #26362 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/test-infra repository. |
|
/cherrypick enterprise-4.3 |
|
@bobfuru: new pull request created: #26363 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/test-infra repository. |
We don't support using newer boot media to add nodes to a clusters.