-
Notifications
You must be signed in to change notification settings - Fork 71
Add support for multiple nics with vmware cloud director in the UI #7452
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]>
|
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. |
KhizerRehan
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.
Minor Feedback (PTAL)
modules/web/src/app/node-data/basic/provider/vmware-cloud-director/template.html
Outdated
Show resolved
Hide resolved
modules/web/src/app/node-data/basic/provider/vmware-cloud-director/component.ts
Outdated
Show resolved
Hide resolved
|
/ok-to-test |
…ctor/template.html Co-authored-by: Khizer Rehan <[email protected]> Signed-off-by: Kai Fink <[email protected]>
…ctor/component.ts Co-authored-by: Khizer Rehan <[email protected]> Signed-off-by: Kai Fink <[email protected]>
Signed-off-by: Kai Fink <[email protected]>
|
@4ch3los can you run |
@KhizerRehan |
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 |
Signed-off-by: Kai Fink <[email protected]>
Signed-off-by: Kai Fink <[email protected]>
Signed-off-by: Kai Fink <[email protected]>
Signed-off-by: Kai Fink <[email protected]>
Signed-off-by: Kai Fink <[email protected]>
Signed-off-by: Kai Fink <[email protected]>
Signed-off-by: Kai Fink <[email protected]>
|
Hey There! OSM and Machinecontroller changes have been released and i updated the dependencies, client, codegen etc. the only thing failing is the unit tests, but im not exactly sure why, does anybody of you have a hint? @KhizerRehan @Waseem826 |
KhizerRehan
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.
Minor Feedback
|
|
||
| private _initForm(): void { | ||
| const values = this._nodeDataService.nodeData.spec.cloud.vmwareclouddirector; | ||
| const defaults = getDefaultNodeProviderSpec(NodeProvider.VMWARECLOUDDIRECTOR) as VMwareCloudDirectorNodeSpec; |
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.
Please add default value for additional network in getDefaultNodeProviderSpec method under case NodeProvider.VMWARECLOUDDIRECTOR:
additionalNetworks: []
|
/test pre-dashboard-api-unit |
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.
Pull Request Overview
This PR adds support for configuring multiple network interfaces for VMware Cloud Director worker nodes in the UI, complementing backend support added in related machine-controller and operating-system-manager PRs. Users can now specify additional networks beyond the primary network when creating machine deployments.
Key Changes:
- Added
additionalNetworksfield to VMware Cloud Director node specifications across frontend and backend - Implemented UI controls for selecting multiple networks with validation to prevent duplicate selection
- Updated network configuration logic to handle both primary and additional networks as a unified list
Reviewed Changes
Copilot reviewed 14 out of 15 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| modules/web/src/app/shared/entity/node.ts | Added additionalNetworks array field to VMwareCloudDirectorNodeSpec |
| modules/web/src/app/node-data/basic/provider/vmware-cloud-director/template.html | Added multi-select dropdown for additional networks with conditional display |
| modules/web/src/app/node-data/basic/provider/vmware-cloud-director/component.ts | Implemented logic for managing additional networks selection and synchronization |
| modules/api/pkg/resources/machine/common.go | Updated provider config generation to merge primary and additional networks into unified list |
| modules/api/pkg/machine/convert.go | Added conversion logic between machine spec networks and API node spec format |
| modules/api/pkg/api/v1/types.go | Added AdditionalNetworks field to VMwareCloudDirectorNodeSpec type |
| modules/api/pkg/test/e2e/utils/apiclient/models/*.go | Regenerated OpenAPI client models for new fields and Kubernetes API updates |
| modules/api/go.mod | Updated dependencies including k8s.io, controller-runtime, and related libraries |
| modules/api/cmd/kubermatic-api/swagger.json | Updated swagger specification with new field definitions |
| modules/api/pkg/test/e2e/utils/kubernetes.go | Updated RESTClientForGVK call signature for new API version |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| const networkControl = this.form.get(Controls.Network); | ||
| const additionalNetworksControl = this.form.get(Controls.AdditionalNetworks); | ||
|
|
||
| additionalNetworksControl.setValue(additionalNetworksControl.value.filter(n => this.networks.includes(n))); |
Copilot
AI
Nov 5, 2025
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.
Potential nil reference if additionalNetworksControl.value is null or undefined. Add a null check before calling filter: additionalNetworksControl.value?.filter(n => this.networks.includes(n)) ?? []
| additionalNetworksControl.setValue(additionalNetworksControl.value.filter(n => this.networks.includes(n))); | |
| additionalNetworksControl.setValue(additionalNetworksControl.value?.filter(n => this.networks.includes(n)) ?? []); |
|
FYI: @4ch3los The following test case failures are due to dependency updates the Ref: #7692 |
|
@4ch3los can you rebase your PR with latest main branch? |
# Conflicts: # modules/api/go.mod # modules/api/go.sum
|
@4ch3los: The following tests failed, say
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. |
Did it, and seems that the pipeline failed cause of some temporary conditions again |

What this PR does / why we need it:
This PR completes the feature of multiple nics for vmware cloud director workers(introduced in kubermatic/machine-controller#1941 & kubermatic/operating-system-manager#471 ). By Allowing to define additional networks, which will also be added to the machinedeployment
Which issue(s) this PR fixes:
What type of PR is this?
/kind feature
Special notes for your reviewer:
This PR depends on kubermatic/machine-controller#1941 & kubermatic/operating-system-manager#471
Does this PR introduce a user-facing change? Then add your Release Note here:
Documentation: