Skip to content

Addressing issue of wrongly freeing un- or StatefulSet managed Pod IPs#5

Merged
Levovar merged 1 commit intomasterfrom
cluster_restart
Mar 26, 2020
Merged

Addressing issue of wrongly freeing un- or StatefulSet managed Pod IPs#5
Levovar merged 1 commit intomasterfrom
cluster_restart

Conversation

@Levovar
Copy link
Copy Markdown
Collaborator

@Levovar Levovar commented Mar 12, 2020

Supposed to fix #4
Changing Pod name check to also compare Pod UID when deciding if a Pod belongs to a DanmEp, or not.
This is needed to be able to definitively decide if a DanmEp's Pod exists, or not.
Also added a delay, and a re-check before we free an IP to avod accidentally racing with an ongoing CNI operation.
Lastly, to be inline with recent upstream DANM change DanmEp is not cleared anymore when an IP could not be freed for some reason.
This will result in a retrial during the next periodic tick.

@Levovar Levovar changed the title Addressing issue of wrongly freeing un or StatefulSet managed Pod IPs Addressing issue of wrongly freeing un- or StatefulSet managed Pod IPs Mar 12, 2020
This is needed to be able to definitively decide if a DanmEp's Pod exists, or not.
Also added a delay, and a re-check before we free an IP to avod accidentally racing with an ongoing CNI operation.
Lastly, to be inline with recent upstream DANM change DanmEp is not cleared when an IP could not be freed for some reason.
It iwll result ins a retrial during the next periodic tick.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

IP address for statefulset pod is released by mistake

1 participant