-
Notifications
You must be signed in to change notification settings - Fork 481
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
vSphere IPI Support for Static IPs #1267
vSphere IPI Support for Static IPs #1267
Conversation
Skipping CI for Draft Pull Request. |
20c22ff
to
82ce751
Compare
b123e68
to
9b0e10e
Compare
4e3d973
to
0979350
Compare
e6067ee
to
5cfeab4
Compare
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.
@rvanderp3 Overall LGTM. A few nit comments and lint failing fixes.
/override markdownlint |
@rvanderp3: /override requires failed status contexts, check run or a prowjob name to operate on.
Only the following failed contexts/checkruns were expected:
If you are trying to override a checkrun that has a space in it, you must put a double quote on the context. In 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. |
/lgtm |
/approve |
/retest |
/hold |
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.
Nothing blocking from my side assuming my understanding of hive's day 0 approach is correct. Whether/how hive will support this via MachinePools is out of scope, but looks doable based on what I see here.
Otherwise, just nits and questions.
/approve
3. For compute nodes, produce machine manifests with associated network device configuration. | ||
4. For bootstrap and control plane nodes, modify vSphere terraform to convert network device configuration to a VM guestinfo parameter for each VM to be created. | ||
|
||
As the assets are generated for the control plane and compute nodes, the slice of `host`s for each node role will be used to populate network device configuration. The number of `host`s must match the number of replicas defined in the associated machine pool. |
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.
Is static IP support on the roadmap for you?
We're trying to do as little as we can get away with in this space until we know how the CAPI transition is going to shake out for us. That said...
For day 0 we accept the install-config as an opaque blob and pass it through. Since it appears possible to do this new thing with just install-config (i.e. you don't have to hand-edit manifests* -- right?) I think we can have day 0 support for free.
For day 2, we'll need to figure out how/whether (hive) MachinePools will be supported.
- If yes, we would need to figure out how to allow the user to plumb the new
addressesFromPools
through. (And we'll need to address how that IPAddressPool is managed; probably punted to however the user sees fit -- possibly from the hub via syncsets, but otherwise directly on the spoke.) - If no, we either have to document "no support" and let things break organically if the user tries to use MachinePools with this feature; or, if that organic breakage is really terrible, try to discover whether static IPs are in play (by parsing the install-config -- is there another way?) and forbid MachinePools proactively.
*We do have a code path to muck with the generated machineset manifests for a couple of (specific, hardcoded) things. But it would be nice to avoid adding more to that if possible.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 2uasimojo, patrickdillon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test markdownlint |
/lgtm |
/lgtm |
/hold cancel |
Spoke with @rvanderp3 , looks like the template changed mid way through this one |
@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/markdownlint In 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. |
@rvanderp3: 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/test-infra repository. I understand the commands that are listed here. |
cc: @JoelSpeed, @elmiko, @patrickdillon, @jcpowermac, @cybertron, @zaneb