-
Notifications
You must be signed in to change notification settings - Fork 258
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
hubble-relay pods are not starting if hubble.listenAddress is set to 127.0.0.1:4244 #1663
Comments
with
with
Sorry havn't copied the pod logs. I'm using |
I also see no way to set multiple addresses. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Description:
If i deploy cilium (via helm) and set
hubble.enable=true
andhubble.listenAddress=127.0.0.1:4244
, thehubble-relay
pods are not able to get ready.I want to set the IP to limit the potential attck surface on our nodes, most of them have 2 NICs, one for INET traffic and the other NIC for LAN traffic. Actually i see no way to prevent hubble from listening on every addresses.
The only way i have is to set the host firewall, which can be challenging (many different host configurations, so not every node has an equal configuration).
My actual test deployments (K3s) are on a staging cluster (just 2 nodes), with an Debian 12 minimal setup.
This is how my actual
values.yaml
look like..The text was updated successfully, but these errors were encountered: