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

Client IPAM negotiation not working properly #802

Closed
Schille opened this issue Feb 24, 2025 · 0 comments · Fixed by #803
Closed

Client IPAM negotiation not working properly #802

Schille opened this issue Feb 24, 2025 · 0 comments · Fixed by #803
Labels
bug 🐛 Something isn't working good first issue ✨ Good for newcomers

Comments

@Schille
Copy link
Collaborator

Schille commented Feb 24, 2025

What happened?

I wanted to connect with a Gefyra client to a cluster. After some short time, the connection process was aborted with the message Error: could not connect. Not much more information either.

What did you expect to happen?

Gefyra to connect successfully.

Please provide the output of gefyra check.

How can we reproduce it (as minimally and precisely as possible)?

Connect a Gefyra client from a fresh environment (for example with Docker Desktop) with a cluster that already has some other clients connected (the more the better).

What Kubernetes setup are you working with?

OS version

Anything else we need to know?

The current implementation for the IPAM negotiation between the client and the operator does not properly work. In fact, the client always tries the same IPAM repeatedly until this stops with an error.

Either, the client queries all taken IPAMs from other clients (via GefyraClient.providerParameter) or tries different IPAMs during the connection sequence.
I'd opt for the first solution, as this will lead to a deterministic IPAM negotiation.

@SteinRobert SteinRobert added bug 🐛 Something isn't working good first issue ✨ Good for newcomers labels Feb 26, 2025
SteinRobert added a commit that referenced this issue Feb 26, 2025
SteinRobert added a commit that referenced this issue Feb 26, 2025
SteinRobert added a commit that referenced this issue Feb 26, 2025
SteinRobert added a commit that referenced this issue Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Something isn't working good first issue ✨ Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants