Only pull the aws resources from its own VPC#41783
Conversation
|
/test |
|
@HadrienPatte thanks for the review. I will adjust those changes later today. I actually have a question for you since datadog is using the ENI GC where I didn't do the filter for that call. Do you think that will help you? I remember there was a PR from the datadog saying that you have to set the max result to 1000 for ENI if I'm not mistaken. |
I don't think it's necessary to add VPC filtering to the ENI GC logic as it is already filtering on cluster name which should be more fine grained than VPC ID. |
yes, if using the default name. no, if using the user defined name. Maybe we should append the user define tag with default tags to resolve this particular issue |
2dc31f6 to
ff60513
Compare
|
/test |
7a3718f to
784d0c4
Compare
784d0c4 to
1d5ce34
Compare
pippolo84
left a comment
There was a problem hiding this comment.
Thanks! 💯
LGTM minus a non-blocking nit left inline.
1d5ce34 to
2824277
Compare
|
/test |
2824277 to
504375b
Compare
|
/test |
Make the aws operator to figure out its own vpcID to filter common AWS resources to reduce the aws calls and operator's CPU and memory pressure. Signed-off-by: Liyi Huang <liyi.huang@isovalent.com>
Refactor metadata package and related var and add metadata_mock so we can properly perform the test for aws pkg. Signed-off-by: Liyi Huang <liyi.huang@isovalent.com>
504375b to
96ab3ec
Compare
|
/test |
|
@liyihuang @joamaki , can we get this merged before the next patch release? |
|
this is pending review from @hemanthmalla. If it get approves, I dont know if we can backport to 1.18 since we usually only backport the bug fix. |
|
@liyihuang We'd love to start testing this via the |
|
I dont have the permission to merge PR to main. I guess if you want to test now, you can test the PR image and chart. You can find it here https://github.com/cilium/cilium/actions/runs/17964550021/job/51094783064?pr=41783. |
|
Merging this since all the comments have been addressed and it is also blocking #41954 |
This PR will make aws operator to read the metadata info to get its own VPC ID and use it as filter before it pulls the aws vpc/subnet/route/security group so it can reduce the cpu/memory and other potential issues(like too many responds causing ec2 client timeout etc)
With this PR, we will see the that we only sync one VPC
without this PR, in the same AWS account, we can see that we sync other resources from other VPCs
Fixes: #41392