Some IPv4 connectivity tests still run even with ipv4.enabled=false #2529
Labels
kind/bug
Something isn't working
kind/community-report
This was reported by a user in the Cilium community, eg via Slack.
needs/triage
This issue requires triaging to establish the root cause.
Is there an existing issue for this?
What happened?
Running, for example:
When cilium is installed via helm chart (terraform) in chaining mode with AWS VPC CNI on IPv6 dualstack network with IPv6 being primary protocol (private subnets are ipv6 only, public are dualstack for backwards compat)
All values used:
Output of the test:
You can see that IPv6 tests pass, but IPv4 tests fail as expected. However, other IPv4 tests do not run when chart is installed with
ipv4.enabled=false
.Cilium Version
1.15.4
Kernel Version
6.1.82-99.168.amzn2023.x86_64 cilium/cilium#1 SMP PREEMPT_DYNAMIC Mon Mar 25 17:11:31 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Kubernetes Version
v1.29.3-eks-adc7111
Regression
No response
Sysdump
No response
Relevant log output
No response
Anything else?
No response
Cilium Users Document
Code of Conduct
The text was updated successfully, but these errors were encountered: