NodePort fails when using IP attached to interface without HW address #12317
Labels
kind/community-report
This was reported by a user in the Cilium community, eg via Slack.
needs/triage
This issue requires triaging to establish severity and next steps.
priority/high
This is considered vital to an upcoming release.
sig/datapath
Impacts bpf/ or low-level forwarding details, including map management and monitor messages.
Bug report
General Information
How to reproduce the issue
When deploying Cilium, network iface auto-discovery doesn't work with our networking design. We need to explicitly define
--global.devices=eth0
to have Cilium running, but in this configuration, we are not able to establish a connection to a NodePort service.I can provide some details on our network stack :
With this setup, Cilium's startup script is not able to detect eth0 as network interface
If i specify the flag --global.devices=eth0, and i a create a NodePort service, i'm not able to establish a connection to the IP specified on the 'lo' iface from outside of the cluster.
Establishing a connection to 10.189.20.54:31619 fail.
The text was updated successfully, but these errors were encountered: