spegel icon indicating copy to clipboard operation
spegel copied to clipboard

Helm Chart NODE_IP should be optionally configurable.

Open rsavage-nozominetworks opened this issue 1 year ago • 4 comments

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 the NODE_IP optionally configured if needed.

EKS Version: 1.28 Spegel version: v0.0.16

rsavage-nozominetworks avatar Dec 12 '23 22:12 rsavage-nozominetworks

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?

phillebaba avatar Dec 18 '23 12:12 phillebaba

BTW I created a PR for this fix already here.

Hi there, the error:

Dec 29 00:27:49 eks-node-1 containerd[2413588]: time="2023-12-29T00:28:49.669982205Z" level=info msg="trying next host" error="failed to do request: Head \"http://127.0.0.1:30021/REDACTED/REDACTED/REDACTED/REDACTED/manifests/ed7e4e82?ns=ghcr.io\": dial tcp 127.0.0.1:30021: i/o timeout" host="127.0.0.1:30021"

rsavage-nozominetworks avatar Jan 11 '24 23:01 rsavage-nozominetworks

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!

Giaco9 avatar May 21 '24 15:05 Giaco9

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!

Giaco9NN avatar Sep 05 '24 06:09 Giaco9NN

Fixed by #578

phillebaba avatar Oct 04 '24 08:10 phillebaba