[e2e] Add test cases for pre-created VPC #933
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wenyingd
force-pushed
the
e2e_pre_vpc
branch
from
f4efb12 to
b818bc0
Compare
|
/e2e |
wenyingd
force-pushed
the
e2e_pre_vpc
branch
from
b818bc0 to
336b301
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #933 +/- ##
=======================================
Coverage 73.37% 73.37%
=======================================
Files 118 118
Lines 16394 16394
=======================================
Hits 12029 12029
Misses 3581 3581
Partials 784 784
|
|
/e2e |
1 similar comment
|
/e2e |
wenyingd
force-pushed
the
e2e_pre_vpc
branch
from
336b301 to
e55f61d
Compare
|
/e2e |
wenyingd
force-pushed
the
e2e_pre_vpc
branch
from
509290d to
7b88c8a
Compare
wenyingd
force-pushed
the
e2e_pre_vpc
branch
from
7b88c8a to
c6cc042
Compare
|
/e2e |
1 similar comment
|
/e2e |
wenyingd
force-pushed
the
e2e_pre_vpc
branch
4 times, most recently
from
db80623 to
994ada6
Compare
|
/e2e |
|
/e2e |
1 similar comment
|
/e2e |
wenyingd
force-pushed
the
e2e_pre_vpc
branch
from
994ada6 to
93f8915
Compare
|
/e2e |
2 similar comments
|
/e2e |
|
/e2e |
wenyingd
force-pushed
the
e2e_pre_vpc
branch
from
93f8915 to
c6cca51
Compare
|
/e2e |
wenyingd
force-pushed
the
e2e_pre_vpc
branch
from
c6cca51 to
18ad4b0
Compare
This change is to add a new end-to-end test for the pre-created VPC, it includes these steps, 1. Create a VPC/LBS/Attachment on NSX 2. Create a Namespace on vCenter or K8s, which depends on if the setup is a wcp testbed or not. Note, it planned to run the test on wcp testbed, please provide a valid pair of vc-user and vc-password which has the permission to create instance on vCenter 3. Create LoadBalancer typed Service inside the Namespace 4. Create server Pod for the LoadBalancer typed Service 5. Create client Pod in the same Namespace 6. Verified the traffic from the client Pod to the LoadBalancer's external IP 7. Delete LoadBalancer typed Service and verified that the realted NSX resources are removed as expected 8. Delete the Namespace from vCenter or K8s 9. Delete the VPC from NSX
wenyingd
force-pushed
the
e2e_pre_vpc
branch
from
18ad4b0 to
f9ba87d
Compare
|
/e2e |
1 similar comment
|
/e2e |
zhengxiexie
approved these changes
Dec 17, 2024
wenqiq
reviewed
Dec 17, 2024
wenqiq
approved these changes
Dec 17, 2024
wenyingd
added a commit
to wenyingd/nsx-operator
that referenced
this pull request
Dec 17, 2024
This change is to add a new end-to-end test for the pre-created VPC, it includes these steps, 1. Create a VPC/LBS/Attachment on NSX 2. Create a Namespace on vCenter or K8s, which depends on if the setup is a wcp testbed or not. Note, it planned to run the test on wcp testbed, please provide a valid pair of vc-user and vc-password which has the permission to create instance on vCenter 3. Create LoadBalancer typed Service inside the Namespace 4. Create server Pod for the LoadBalancer typed Service 5. Create client Pod in the same Namespace 6. Verified the traffic from the client Pod to the LoadBalancer's external IP 7. Delete LoadBalancer typed Service and verified that the realted NSX resources are removed as expected 8. Delete the Namespace from vCenter or K8s 9. Delete the VPC from NSX
wenyingd
added a commit
that referenced
this pull request
Dec 18, 2024
This change is to add a new end-to-end test for the pre-created VPC, it includes these steps, 1. Create a VPC/LBS/Attachment on NSX 2. Create a Namespace on vCenter or K8s, which depends on if the setup is a wcp testbed or not. Note, it planned to run the test on wcp testbed, please provide a valid pair of vc-user and vc-password which has the permission to create instance on vCenter 3. Create LoadBalancer typed Service inside the Namespace 4. Create server Pod for the LoadBalancer typed Service 5. Create client Pod in the same Namespace 6. Verified the traffic from the client Pod to the LoadBalancer's external IP 7. Delete LoadBalancer typed Service and verified that the realted NSX resources are removed as expected 8. Delete the Namespace from vCenter or K8s 9. Delete the VPC from NSX
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change is to add a new end-to-end test for the pre-created VPC, it includes these steps,