-
Notifications
You must be signed in to change notification settings - Fork 1.9k
OSDOCS-988 vSphere IPI #22485
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
OSDOCS-988 vSphere IPI #22485
Conversation
|
The preview will be available shortly at: |
|
@patrickdillon, will you PTAL? |
installing/installing_vsphere/installing-vsphere-installer-provisioned.adoc
Outdated
Show resolved
Hide resolved
patrickdillon
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 left a few comments. we also need to update upi docs for 4.5 & 4.4:
- folder name - https://github.com/openshift/installer/pull/3738/files
- machinesets - openshift/installer#3619
|
Thank you @patrickdillon! I've made the updates that you requested in-line and will address the other changes that you pointed out on https://bugzilla.redhat.com/show_bug.cgi?id=1849434. @gpei, will you PTAL? |
|
@jinyunma could you help to check this ? |
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.
The default storage for each node is 120G, plus 1 template with 16G, so the minimum size of storage required is 856 GB.
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.
this is technically correct. for vanilla ipi install bootstrap node will be torn down before worker creation so 800 gb is safe. I am fine with bumping as suggested.
@patrickdillon About "folder name", only need to be added into 4.5 upi doc, right? Or you also did some change on 4.4? |
|
Another comment is after installing a ipi cluster on vsphere, also need the step of Image registry storage configuration, like we do in vsphere upi, |
only 4.5. folder name still == cluster name in 4.4 |
808cd2e to
2f07bda
Compare
lamek
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.
Just a handful of nits. This looks really great.
Acked |
|
For new added section "Installing a cluster on vSphere with customization", missed the networking customization like vsphere upi in section "Installing a cluster on vSphere with user-provisioned infrastructure and network customization", since vsphere ipi installation also supports customized network. |
@jboxman, are you planning on making an assembly for the network config for vSphere IPI? |
|
@kalexand-rh, I can. |
|
@jinyunma, do you see any other changes to the documents that are currently in the scope of this PR? |
I checked and all are lgtm, except below two installation configuration parameters in topic "Installing a cluster on vSphere with customizations"[1][2] and removing machinset on all upi on vpshere installation guide.
2.
|
be1e2fd to
2d2a788
Compare
|
@jinyunma, will you please take another look? |
|
|
@kalexand-rh vsphere ipi installation has one known issue bz#1852545 . If vsphere server on customer site have multiple datacenter and clusters, then it will have multiple default root resource pool, the worker nodes will not be provisioned successfully during installation. Do you think it is good way to add the issue into known issue list in 4.5 release notes or add a note in ipi on vsphere installation doc? If need workaround, @patrickdillon may help to provide it. |
|
@jinyunma, I will check on bz#1852545 and tag you in whatever follow-up PR I open. |
49f47fd to
057d80e
Compare
|
/cherrypick enterprise-4.5 |
|
@kalexand-rh: new pull request created: #23552 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. |
https://issues.redhat.com/browse/OSDOCS-988