Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

IP addresses still allocated to completed pods #294

Closed
ac-hibbert opened this issue Jan 22, 2019 · 3 comments
Closed

IP addresses still allocated to completed pods #294

ac-hibbert opened this issue Jan 22, 2019 · 3 comments
Labels
priority/P1 Must be staffed and worked currently or soon. Is a candidate for next release
Milestone
v1.5

Comments

@ac-hibbert
Copy link

Hi,

We have some CronJobs that run hourly and then the pods return to Completed. It looks like the IP address is still in use. The ENI itself is still in use with other secondary IPs. But wandering why this stays as "In Use" despite the cronjob being complete and no pods are running? Also what is the cooling period?

Thanks
@mogren
Copy link
Contributor

mogren commented Jan 22, 2019

Hi @Hibbert!

The reasons we have the IPs around is an optimization. Also, they are not allocated to the pods, but kept as a "warm pool" per ENI for the CNI plugin to pick from when attaching IPs to new pods. Some more details in my reply on issue 123.

@tabern tabern mentioned this issue Mar 1, 2019
Closed
@tabern tabern added this to the v1.4 milestone Mar 1, 2019
@tabern tabern added the priority/P1 Must be staffed and worked currently or soon. Is a candidate for next release label Mar 1, 2019
@mogren mogren mentioned this issue Mar 16, 2019
Closed
@mogren
Copy link
Contributor

mogren commented Mar 29, 2019

I've added some improved logging, but not been able to track down the issue. Punting this issue to 1.5.

@mogren mogren modified the milestones: v1.4, v1.5 Mar 29, 2019
@mogren mogren mentioned this issue May 10, 2019
Merged
@mogren
Copy link
Contributor

mogren commented Jun 5, 2019

Resolving since v1.5.0 is released. If you want the IPs to be released from attached ENIs, please set the WARM_IP_TARGET environment variable.

@mogren mogren closed this as completed Jun 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority/P1 Must be staffed and worked currently or soon. Is a candidate for next release
Projects
None yet
Milestone
v1.5
Development

No branches or pull requests
3 participants
@mogren @ac-hibbert @tabern