You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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?
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"
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.
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: