cilium: Cilium segfaults with --enable-l7-proxy=false
Is there an existing issue for this?
- I have searched the existing issues
What happened?
A user reports that Cilium hit a segfault when the l7 proxy was disabled.
Cilium Version
1.11.1
Kernel Version
n/a
Kubernetes Version
n/a
Sysdump
No response
Relevant log output
[cilium-ptl2k cilium-agent] panic: runtime error: invalid memory address or nil pointer dereference
[cilium-ptl2k cilium-agent] [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1f6243c]
[cilium-ptl2k cilium-agent]
[cilium-ptl2k cilium-agent] goroutine 887 [running]:
[cilium-ptl2k cilium-agent] github.com/cilium/cilium/pkg/proxy.(*Proxy).CreateOrUpdateRedirect(0x0, {0x2c53a30, 0xc00013bf00}, {0xc0044ae750, 0x4}, {0x2cb2e30, 0xc0009ac380}, 0xc0020f3fc0)
Anything else?
No response
Code of Conduct
- I agree to follow this project’s Code of Conduct
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 17 (7 by maintainers)
No L7 policies:
@Preisschild Do you have any visibility annotations on your pods? https://docs.cilium.io/en/stable/policy/visibility/
Simple attempt to fix this: https://github.com/cilium/cilium/pull/19092
Deployed with this values.yaml with helm, single node.
(intentionally garbled some ipv6 addresses in the copy/paste.)
the “full” stacktrace with some pretext also: