feat: enhanced subnet discovery rebase from #3380#3463
Conversation
04dfa96 to
ed16c61
Compare
|
This pull request 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 |
b42d116 to
e105464
Compare
1bf9f7a to
c4cef04
Compare
Pavani-Panakanti
left a comment
There was a problem hiding this comment.
What is the rollback behavior to previous versions which won't have this feature ?
- Will there be any leaked ENI's that were created in secondary subnets as older version of CNI will not be aware of these ?
- Will there be any leaked pod ips which were assigned from secondary subnet ENI's ?
c4cef04 to
1ba4da9
Compare
New ENIs have the same tags as today's ENIs and will be cleaned up by sweepers in case of leaking. Rollback will need downgrading the version and recycle nodes. |
66bdcad to
73a0b46
Compare
|
Added a comment, rest of the changes looks good to me |
|
can you also refer to this code coverage report https://app.codecov.io/github/aws/amazon-vpc-cni-k8s/pull/3463. I think in awsutils.go there many missed lines. If you have added them do consider adding unit test to them. Lets make sure we atleast cover critical or tricky parts. |
76ef0ad to
b77ecd8
Compare
|
Thanks Hao for the changes !! |
b77ecd8 to
a8d36df
Compare
a8d36df to
8ef611f
Compare
What type of PR is this?
Which issue does this PR fix?:
What does this PR do / Why do we need it?:
The is a feature PR and rebased from #3380
Testing done on this change:
Will this PR introduce any new dependencies?:
Will this break upgrades or downgrades? Has updating a running cluster been tested?:
Does this change require updates to the CNI daemonset config files to work?:
Does this PR introduce any user-facing change?:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.