-
Notifications
You must be signed in to change notification settings - Fork 64
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
KubeVirt: Support for VPC and Subnets #6941
KubeVirt: Support for VPC and Subnets #6941
Conversation
Signed-off-by: Waleed Malik <[email protected]>
Signed-off-by: Waleed Malik <[email protected]>
Signed-off-by: Waleed Malik <[email protected]>
/retest |
@ahmedwaleedmalik Any idea what we need to do to get this PR merged ? |
We couldn't test it previously because of the issues with dev. @Waseem826 is currently reviewing it and i'm testing the final parts. |
Signed-off-by: Waleed Malik <[email protected]>
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.
/approve
LGTM label has been added. Git tree hash: cb7d8f7d3efd1a02e39841e90ee68b3d53c78ae6
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Waseem826 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 |
/cherry-pick release/v2.26 |
@ahmedwaleedmalik: new pull request created: #6963 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-sigs/prow repository. |
What this PR does / why we need it:
Builds on top of kubermatic/machine-controller#1862 and adds support on UI for using VPC at cluster level and subnets and machine level.
Short demonstration of the feature
Screen.Recording.2024-10-18.at.15.27.53.mov
Which issue(s) this PR fixes:
Fixes #
What type of PR is this?
/kind feature
Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:
Documentation: