Add integration test for Pod delete #569
Open
+185
−0
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.
Issue #, if available:
Description of changes:
Test passes:
Branch ENI Pods Test Network Connectivity on Delete and Recreation of Pod creating statefulset with network connectivity when statefulset is created with network connectivity requirements should have all pods running with network access
/home/supreeet/workspaces/vpc-cni/amazon-vpc-resource-controller-k8s/test/integration/perpodsg/perpodsg_test.go:561
STEP: creating the namespace if not exist @ 06/10/25 09:06:16.007
STEP: creating security group policy @ 06/10/25 09:06:16.018
STEP: creating the security group policy @ 06/10/25 09:06:16.018
STEP: creating statefulset @ 06/10/25 09:06:16.028
STEP: waiting for statefulset pods to be ready @ 06/10/25 09:06:16.041
STEP: verifying network connectivity of all pods @ 06/10/25 09:06:21.142
STEP: getting the pod belonging to the deployment @ 06/10/25 09:06:31.142
STEP: getting the branch ENI from the pod's annotation @ 06/10/25 09:06:31.143
STEP: Verifying for ENI ID: eni-0707914300fef8c34 ENI IP: 192.168.11.171 Pod Name: per-pod-sg/network-test-0 Pod's IP: 192.168.11.171 @ 06/10/25 09:06:31.143
STEP: getting the security group for the ENI from AWS EC2 @ 06/10/25 09:06:31.143
STEP: getting the branch ENI from the pod's annotation @ 06/10/25 09:06:31.254
STEP: Verifying for ENI ID: eni-07f8b5b81c6d69179 ENI IP: 192.168.36.27 Pod Name: per-pod-sg/network-test-1 Pod's IP: 192.168.36.27 @ 06/10/25 09:06:31.254
STEP: getting the security group for the ENI from AWS EC2 @ 06/10/25 09:06:31.255
STEP: force deleting one pod to verify recreation @ 06/10/25 09:06:31.366
STEP: waiting for pod to be recreated @ 06/10/25 09:06:31.385
STEP: verifying network connectivity after pod recreation @ 06/10/25 09:06:31.386
STEP: getting the pod belonging to the deployment @ 06/10/25 09:06:41.386
STEP: getting the branch ENI from the pod's annotation @ 06/10/25 09:06:41.386
STEP: Verifying for ENI ID: eni-08814d938bcc167d2 ENI IP: 192.168.30.67 Pod Name: per-pod-sg/network-test-0 Pod's IP: 192.168.30.67 @ 06/10/25 09:06:41.386
STEP: getting the security group for the ENI from AWS EC2 @ 06/10/25 09:06:41.386
STEP: getting the branch ENI from the pod's annotation @ 06/10/25 09:06:41.497
STEP: Verifying for ENI ID: eni-07f8b5b81c6d69179 ENI IP: 192.168.36.27 Pod Name: per-pod-sg/network-test-1 Pod's IP: 192.168.36.27 @ 06/10/25 09:06:41.497
STEP: getting the security group for the ENI from AWS EC2 @ 06/10/25 09:06:41.497
STEP: deleting the statefulset @ 06/10/25 09:06:41.607
STEP: deleting security group policy @ 06/10/25 09:06:41.616
STEP: deleting the namespace @ 06/10/25 09:06:43.626
• [33.628 seconds]