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.

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

IP reclaim for various scenarios #2967

Closed
weizhoublue opened this issue Dec 20, 2023 · 3 comments · Fixed by #3081
Closed

IP reclaim for various scenarios #2967

weizhoublue opened this issue Dec 20, 2023 · 3 comments · Fixed by #3081

Comments

@weizhoublue
Copy link
Collaborator

What would you like to be added?

1 split SPIDERPOOL_GC_TERMINATING_POD_IP_ENABLED to
gc terminating pod on not-ready node
gc terminating timeout pod on ready node

2 for ip conflict detecting of coordinate, when detecting a bad IP, it could trigger the IPAM to release assigned IP, and make it possible to assign a new good IP for next turn

Why is this needed?

No response

How to implement it (if possible)?

No response

Additional context

No response

@Icarus9913
Copy link
Collaborator

next version

@ty-dc
Copy link
Collaborator

ty-dc commented Dec 29, 2023

[root@controller-node-1 ~]# kubectl get po -owide | grep 192.230.10.111
test-pod-6d474d8898-bb5qh     0/1     Terminating   5          131m   192.230.10.111   worker-node-3   <none>           <none>
test-pod-6f98fb4cd5-qsp9g     1/1     Running       0          126m   192.230.10.111   worker-node-3   <none>           <none>

@ty-dc
Copy link
Collaborator

ty-dc commented Jan 29, 2024

fix #3081 and #3002

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants