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

vSphere IPI Support for Static IPs #1267

Merged

Conversation

rvanderp3
Copy link
Contributor

@rvanderp3 rvanderp3 commented Oct 19, 2022

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 19, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 19, 2022

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@rvanderp3 rvanderp3 force-pushed the static-ip-addresses-vsphere branch 3 times, most recently from 20c22ff to 82ce751 Compare October 21, 2022 20:43
@rvanderp3 rvanderp3 changed the title [WIP] enhancement proposal for vSphere static IPs [WIP] vSphere IPI Support for Static IPs Oct 21, 2022
@rvanderp3 rvanderp3 force-pushed the static-ip-addresses-vsphere branch 4 times, most recently from b123e68 to 9b0e10e Compare October 24, 2022 17:38
@rvanderp3 rvanderp3 changed the title [WIP] vSphere IPI Support for Static IPs vSphere IPI Support for Static IPs Oct 24, 2022
@rvanderp3 rvanderp3 marked this pull request as ready for review October 24, 2022 17:40
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 24, 2022
@openshift-ci openshift-ci bot requested review from danwinship and dougbtv October 24, 2022 17:42
@rvanderp3 rvanderp3 force-pushed the static-ip-addresses-vsphere branch 8 times, most recently from 4e3d973 to 0979350 Compare October 24, 2022 19:53
Copy link
Contributor

@mtulio mtulio left a 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.

enhancements/network/static-ip-addresses-vsphere.md Outdated Show resolved Hide resolved
enhancements/network/static-ip-addresses-vsphere.md Outdated Show resolved Hide resolved
enhancements/network/static-ip-addresses-vsphere.md Outdated Show resolved Hide resolved
@rvanderp3
Copy link
Contributor Author

/override markdownlint

Copy link
Contributor

openshift-ci bot commented Apr 10, 2024

@rvanderp3: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • markdownlint

Only the following failed contexts/checkruns were expected:

  • ci/prow/markdownlint
  • pull-ci-openshift-enhancements-master-markdownlint

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:

/override markdownlint

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.

@mtulio
Copy link
Contributor

mtulio commented Apr 10, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 10, 2024
@patrickdillon
Copy link
Contributor

/approve

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 10, 2024
@patrickdillon
Copy link
Contributor

/retest

@rvanderp3
Copy link
Contributor Author

/hold
/skip markdownlint

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 10, 2024
Copy link
Member

@2uasimojo 2uasimojo left a 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

enhancements/network/static-ip-addresses-vsphere.md Outdated Show resolved Hide resolved
enhancements/network/static-ip-addresses-vsphere.md Outdated Show resolved Hide resolved
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.
Copy link
Member

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.

enhancements/network/static-ip-addresses-vsphere.md Outdated Show resolved Hide resolved
enhancements/network/static-ip-addresses-vsphere.md Outdated Show resolved Hide resolved
Copy link
Contributor

openshift-ci bot commented Apr 11, 2024

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@rvanderp3
Copy link
Contributor Author

/test markdownlint

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Apr 12, 2024
@vr4manta
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 12, 2024
@JoelSpeed
Copy link
Contributor

/lgtm

@rvanderp3
Copy link
Contributor Author

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 22, 2024
@JoelSpeed
Copy link
Contributor

Spoke with @rvanderp3 , looks like the template changed mid way through this one
/override ci/prow/markdownlint

Copy link
Contributor

openshift-ci bot commented Apr 22, 2024

@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/markdownlint

In response to this:

Spoke with @rvanderp3 , looks like the template changed mid way through this one
/override ci/prow/markdownlint

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.

Copy link
Contributor

openshift-ci bot commented Apr 22, 2024

@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.

@openshift-merge-bot openshift-merge-bot bot merged commit cf06f94 into openshift:master Apr 22, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.