-
Notifications
You must be signed in to change notification settings - Fork 57
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
Helm Chart NODE_IP should be optionally configurable. #293
Comments
Sorry about the regression issues. Its difficult getting things right as CNIs seem to partially implement standards and cloud providers slightly differ. What is the error that you are specifically seeing when staring Spegel? |
BTW I created a PR for this fix already here. Hi there, the error:
|
Hi @phillebaba 👋, considering @rsavage-nozominetworks already opened a pull request to allow to optionally assign NODE_IP, do you think we could merge it? We are interested in that feature as well. Thank you! |
Hei @phillebaba, the problem persists also in version 0.0.23, which is causing some issues when upgrading to version 0.0.24. The patch we must apply to make it work in our environments compromises all changes to Spegel. Can I do anything to make progress on the pull request linked to this issue? Should I open it again? Thank you! |
I am seeing an issue in AWS EKS where worker nodes are unable to connect to port 30020 of the NODE_IP. By manually patching the daemonset and setting the NODE_IP to
127.0.0.1
this allows Spegel mirroring to work. This issue is being raised to have theNODE_IP
optionally configured if needed.EKS Version:
1.28
Spegel version:
v0.0.16
The text was updated successfully, but these errors were encountered: