-
Notifications
You must be signed in to change notification settings - Fork 137
Add support to provisioning vcloud workers with multiple nics/networks #1941
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
Signed-off-by: Kai Fink <[email protected]>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @4ch3los. Thanks for your PR. I'm waiting for a kubermatic member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/cc |
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.
Some suggestions
if err != nil { | ||
return nil, nil, nil, err | ||
} | ||
|
||
if singleNetwork != "" && len(rawConfig.Networks) == 0 { |
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.
why only if len(Networks) == 0? I suggest to use it anyway, as a first c.Networks
element.
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 can change that if you want, my thoughts were, that you would use one of both and not both, but it wouldnt hurt
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 mean, since this commit will deprecate a single Network
and suggest to use []Network
in code we'd want to use only the new way and somehow convert the old deprecated single Network
to the new []Network
.
My suggestion is this exact convertion.
What this PR does / why we need it:
This pr adds the ability to create machines in vmware cloud director with multiple nics using different networks. This is especially useful when you want to use a additional nic for storage
Which issue(s) this PR fixes:
What type of PR is this?
/kind feature
Special notes for your reviewer:
This change just adds the nic to the vm, for the configuration there is a osm pr kubermatic/operating-system-manager#471
Does this PR introduce a user-facing change? Then add your Release Note here:
Documentation: