ip addresses leaking when there are too many ip in cooldown pool about amazon-vpc-cni-k8s

[orsenthil]

do these within 30s: delete one pod and create two new pod, the last pod will fail by can not assign IP address to pod

The default cooldown period is 30 secs,after which the ips in the cooldown will be made available to the pods. Are you noticing that this isn't happening?

The reason for keeping the warm_ip_target is to ensure that VPC CNI doesn't do an unnecessary EC2 api call, which is avoid running to API throttles.

If tuning of ip cooldown period is preferable, it can be controlled using this flag - https://github.com/aws/amazon-vpc-cni-k8s/?tab=readme-ov-file#ip_cooldown_period-v1150

[abbshr]

I mean during the cooldown period, pod can't get an ip even if there are free ips in vpc subnet, which I think is not being expected. This happens because total ip count - assigned ip count < warm_ip_target, and assigned ip count + cooldown ip count = total ip count. Senthil Kumaran ***@***.***> 于 2024年5月2日周四 04:16写道：

…

do these within 30s: delete one pod and create two new pod, the last pod will fail by can not assign IP address to pod The default cooldown period is 30 secs,after which the ips in the cooldown will be made available to the pods. Are you noticing that this isn't happening? The reason for keeping the warm_ip_target is to ensure that VPC CNI doesn't do an unnecessary EC2 api call, which is avoid running to API throttles. If tuning of ip cooldown period is preferable, it can be controlled using this flag - https://github.com/aws/amazon-vpc-cni-k8s/?tab=readme-ov-file#ip_cooldown_period-v1150 — Reply to this email directly, view it on GitHub <#2896 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAXJWS7VYXAQ4BONAZEOOB3ZAFERBAVCNFSM6AAAAABG23UCQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBZGA3DKNZSGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>