-
Notifications
You must be signed in to change notification settings - Fork 295
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
✨Add NSX-VPC Network Provider Support #2848
✨Add NSX-VPC Network Provider Support #2848
Conversation
|
Welcome @silvery1622! |
Hi @silvery1622. Thanks for your PR. I'm waiting for a kubernetes-sigs 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/test-infra repository. |
57df559
to
d2fcf6e
Compare
/ok-to-test |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2848 +/- ##
==========================================
+ Coverage 63.97% 64.05% +0.07%
==========================================
Files 160 161 +1
Lines 9367 9486 +119
==========================================
+ Hits 5993 6076 +83
- Misses 2914 2947 +33
- Partials 460 463 +3 ☔ View full report in Codecov by Sentry. |
d2fcf6e
to
e90acb8
Compare
/retest |
e90acb8
to
c5c2846
Compare
c5c2846
to
454e015
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.
Thanks for the PR! Just left some nits :-)
I think it would be great to add some test output from your local nsx-vpc setup in the PR comments for reference, as upstream doesn't have such infra to test it in e2e or integration test.
454e015
to
3d1b0c2
Compare
Thanks for @zhanggbj 's comments. |
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.
Generally it looks good :-) Just added some other nits in the second round review.
3d1b0c2
to
3c47661
Compare
3c47661
to
057de59
Compare
057de59
to
4e74865
Compare
@silvery1622 ^^ |
4e74865
to
a380565
Compare
A big thanks to @sbueringer and @chrischdi for the awesome reviews and input. I've managed to deal with most of what you pointed out. The one thing I'm still sorting out is the annotation, but I'm about to kick off some tests without it. Could our goal still be to include this in the v1.10.0 release? |
a380565
to
486263f
Compare
Yup, no worries. We'll release CAPV after CAPI v1.7 (16h April) and I wouldn't block it because of the annotation (see our Slack thread, I think we're also talking about different annotations) |
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 think some of the comments or changes got lost (or not yet pushed). PTAL at the open conversations above
(Please note the "4 hidden conversations" (by GitHub))
99e67d4
to
590d6d5
Compare
I've made some changes based on feedback from the review: Removed NSXTVPCSelectorKey and let GetVMServiceAnnotations returns a blank map. Also updated the UT for it. |
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.
one more readability nit
This commit introduces NSX-T Virtual Private Cloud (NSX-VPC) as a new network provider for the vSphere Supervisor Cluster in anticipation of the upcoming vSphere 9 release. Key Changes: nsx-vpc implemented as a new NetworkProvider using nsx-operator libs. Skipped VM Readiness check as NSX-VPC offers private network access. Added unit tests for NSX-VPC network provider."
590d6d5
to
df04b11
Compare
@silvery1622: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. |
/test ? |
@sbueringer: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
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. |
Thank you very much! Nice work! /lgtm Merge pending CI (want to make sure we don't break CI that close to the release) /test pull-cluster-api-provider-vsphere-e2e-govmomi-conformance-ci-latest-main |
LGTM label has been added. Git tree hash: fdf46b4542c06a6ab564f8d24f9a7a5561129b46
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer 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 |
Updated downstream test log with latest code. |
This commit introduces NSX-T Virtual Private Cloud (nsx-vpc) as a new network provider for the vSphere Supervisor Cluster in anticipation of the upcoming vSphere 9 release. Key Changes:
nsx-vpc implemented as a new NetworkProvider using nsx-operator libs.
Skipped VM Readiness check as nsx-vpc offers private network access.
Added unit tests for nsx-vpc network provider.
What this PR does / why we need it:
The vSphere Supervisor Cluster currently accommodates two network types: vSphere Distributed Switch (VDS) and NSX-T network. With the impending release of vSphere 9, a third network type will be introduced: NSX-T Virtual Private Cloud (nsx-vpc).
To adapt this change, CAPV need to add support for nsx-vpc as a new network provider.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #2847