You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
📋 Test Report [cilium-test-1]
❌ 4/41 tests failed (3/350 actions), 51 tests skipped, 0 scenarios skipped:
Test [client-egress-to-cidrgroup-deny]:
Test [client-egress-to-cidr-deny-default]:
Test [node-to-node-encryption]:
❌ node-to-node-encryption/node-to-node-encryption/ping-ipv4: cilium-test-1/client-7b7776c86b-79xbc (10.100.204.5) -> cilium-test-1/host-netns-mv4m6 (10.100.200.4:0)
Test [check-log-errors]:
❌ check-log-errors/no-errors-in-logs/aksname1234567/kube-system/cilium-bkcgr (cilium-agent)
❌ check-log-errors/no-errors-in-logs/aksname1234567/kube-system/cilium-x4z78 (cilium-agent)
[cilium-test-1] 4 tests failed
Additional:
The pods could successfully start again after I deleted the Cilium Network Policies from the connectivity test that were still there:
client-egress-to-cidrgroup-deny:
Hi @ArkShocer, this has been reported as a bug in cilium/cilium#36494. Recommend that if you are running connectivity tests use Cilium CLI version v0.15.22 as there are potentially breaking changes when using the latest CLI.
Describe the bug
When running an AKS cluster with Cilium and deploying a Cilium NetworkPolicy, the Cilium Agent Pods are going into a crashing state.
To Reproduce
cilium connectivity test
kubectl get pods -n kube-system
and see that cilium pods are in a crashing state:Environment:
KubernetesVersion 1.30.6
Cilium Test:
Additional:
The pods could successfully start again after I deleted the Cilium Network Policies from the connectivity test that were still there:
client-egress-to-cidrgroup-deny:
allow-all-egress
Pod Log:
Also, same issue if I enable the
ACNS
The text was updated successfully, but these errors were encountered: