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

neonvm-controller: rework IPAM #1281

Open

Omrigan opened this issue Feb 24, 2025 · 1 comment

Assignees

Contributor

Omrigan commented Feb 24, 2025

Key issues are:

Leader election times out when the rate of allocations is significant.
When a release of an IP fails, it is not retried, so we have 13k stale allocations.
k8s client is recreated on every request.

Plus a few other things.

Originally posted by @Omrigan in #1278 (comment)

Omrigan self-assigned this

Omrigan mentioned this issue

neonvm-controller: make IPAM code production-ready #1278

Open

Contributor Author

Omrigan commented Feb 25, 2025

One more thing is:

We should have some observability into overlay ip allocations, such as time to allocate an IP and a per-VM metric to indicate it has an overlay ip.

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