-
Notifications
You must be signed in to change notification settings - Fork 1.8k
OSDOCS-16317# Doc update for removal of VMware 7.x and VCF 4.x support. #99835
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
base: main
Are you sure you want to change the base?
Conversation
0dcd6fc
to
8464f0c
Compare
@jcpowermac @gnufied @gcharot PTAL and leave LGTM if everything looks accurate. |
I think we should update VCF support from 4.3+ to 4.4+ instead of 5.0. |
|
||
* You have cluster administrator permissions to execute the required permissions in the vCenter instance hosting your {product-title} cluster. | ||
* Your vSphere ESXi hosts are version 7.0U2 or later. | ||
* Your vSphere ESXi hosts are version 8.0 or later. |
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.
8.0 Update 1 to match what what is in other doc
|
||
* You have cluster administrator permissions to execute the required permissions in the vCenter instance hosting your {product-title} cluster. | ||
* Your vSphere ESXi hosts are version 7.0U2 or later. | ||
* Your vSphere ESXi hosts are version 8.0 or later. |
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.
same
|
||
* You have cluster administrator permissions to execute the required permissions in the vCenter instance hosting your {product-title} cluster. | ||
* Your vSphere ESXi hosts are version 7.0U2 or later. | ||
* Your vSphere ESXi hosts are version 8.0 or later. |
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.
same
* Version {product-version} of {product-title} requires VMware virtual hardware version 15 or later. | ||
* Before upgrading OpenShift 4.12 to OpenShift 4.13, you must update vSphere to *v7.0.2 or later*; otherwise, the OpenShift 4.12 cluster is marked *un-upgradeable*. | ||
* Before upgrading OpenShift 4.12 to OpenShift 4.13, you must update vSphere to *v8.0 or later*; otherwise, the OpenShift 4.12 cluster is marked *un-upgradeable*. |
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.
same
Can we remove the vsphere 7 entries from the doc? Looks a bit brutal. Shouldn't we change the lines instead saying that 7 support is now deprecated (or removed as you prefer). Optionally include "if you have questions, please contact Red Hat support, blabla" Also shouldn't we add a relnote entry ? Last, we have some storage doc sections that are refering to vsphere 7 I suggest you sync up with @lpettyjo |
@sslocket: 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. |
LGTM for change management |
If we're ok to remove the lines without warning then LGTM |
These files also need to be changed: |
Version(s):
4.16+
Issue:
https://issues.redhat.com/browse/OSDOCS-16317
Link to docs preview:
QE review:
Additional information:
CHANGE MANAGEMENT REQUIRED