Cilium Envoy 1.16.5 crashes on systems with IPv6 disabled #36691
Description
Is there an existing issue for this?
- I have searched the existing issues
Version
equal or higher than v1.16.4 and lower than v1.17.0
What happened?
Cilium Envoy pods don't start on systems which have IPv6 disabled, due to hardcoded ::1 address which Envoy claims to be invalid on such systems.
How can we reproduce the issue?
- Install Cilium 1.16.5 with Envoy DaemonSet enabled and IPv6 disabled (e.g. via
ipv6.disable=1flag in grub) - Observe the cilium-envoy pods fall into crashloopbackoff.
Cilium Version
1.16.5
Kernel Version
6.8.0-49-generic
Kubernetes Version
1.30.7+k3s1
Regression
It's a regression, 1.16.4 works.
Sysdump
No response
Relevant log output
[2024-12-18 07:00:59.064][7][info][config] [external/envoy/source/server/configuration_impl.cc:168] loading tracing configuration
[2024-12-18 07:00:59.064][7][info][config] [external/envoy/source/server/configuration_impl.cc:124] loading 0 static secret(s)
[2024-12-18 07:00:59.064][7][info][config] [external/envoy/source/server/configuration_impl.cc:130] loading 6 cluster(s)
[2024-12-18 07:00:59.068][7][info][config] [external/envoy/source/server/configuration_impl.cc:138] loading 2 listener(s)
[2024-12-18 07:00:59.070][7][info][config] [external/envoy/source/server/configuration_impl.cc:168] loading tracing configuration
[2024-12-18 07:00:59.070][7][info][config] [external/envoy/source/server/configuration_impl.cc:124] loading 0 static secret(s)
[2024-12-18 07:00:59.070][7][info][config] [external/envoy/source/server/configuration_impl.cc:130] loading 6 cluster(s)
[2024-12-18 07:00:59.073][7][info][config] [external/envoy/source/server/configuration_impl.cc:138] loading 2 listener(s)
[2024-12-18 07:00:59.073][7][critical][main] [external/envoy/source/server/server.cc:414] error initializing config ' /var/run/cilium/envoy/bootstrap-config.json': malformed IP address: ::1
[2024-12-18 07:00:59.073][7][info][main] [external/envoy/source/server/server.cc:1029] exiting
malformed IP address: ::1Anything else?
I believe that the issue was introduced in this commit, c4b1379. Related issue in Envoy, envoyproxy/envoy#29902. In Cilium it can likely be solved just by adding two conditions to the ConfigMap template.
Cilium Users Document
- Are you a user of Cilium? Please add yourself to the Users doc
Code of Conduct
- I agree to follow this project's Code of Conduct
Metadata
Metadata
Assignees
Labels
Cilium agent related.Impacts proxy components, including DNS, Kafka, Envoy and/or XDS servers.This is a bug in the Cilium logic.This was reported by a user in the Cilium community, eg via Slack.This functionality worked fine before, but was broken in a newer release of Cilium.This issue requires triaging to establish severity and next steps.