amazon-vpc-cni-k8s
amazon-vpc-cni-k8s copied to clipboard
e2e test for custom ENIConfig
Need to add functional tests that validate creating an ENIConfig CRD instance.
- [x] test for specifying ENIConfig for new worker node (with no pods)
- [ ] test for adding ENIConfig to an existing worker node that has pods running on it (and have IPs on the primary ENI)
related: https://github.com/awsdocs/amazon-eks-user-guide/pull/72
First step towards adding these testcases - #1373
Testcase for the below scenario is added -
- Follow this guide to start custom networking - https://docs.aws.amazon.com/eks/latest/userguide/cni-custom-network.html
- Verify seconday ENI attached belong to subnet specified in ENI Config
- Verify new pods get IP from the subnet in ENIConfig
--
- Repeat above test but with creating an ENI Config with name other than the subnet
- Set the variable to ENI Config name ame as label annotation
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days
/not stale
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days
/not stale, only part fixed.
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days
Issue closed due to inactivity.