-
Notifications
You must be signed in to change notification settings - Fork 3.7k
pod-to-host:ping-ipv4-external-ip fails on GKE + KPR #44806
Copy link
Copy link
Open
Labels
area/CIContinuous Integration testing issue or flakeContinuous Integration testing issue or flakearea/kprAnything related to our kube-proxy replacement.Anything related to our kube-proxy replacement.integration/cloudRelated to integration with cloud environments such as AKS, EKS, GKE, etc.Related to integration with cloud environments such as AKS, EKS, GKE, etc.
Description
When KPR is enabled on GKE, the pod-to-host:ping-ipv4-external-ip test fails, with and without policies enforced.
From https://github.com/cilium/cilium/actions/runs/23064464032/job/66999440526:
[.] Action [no-policies/pod-to-host:ping-ipv4-external-ip: cilium-test-1/client2-d56fbd75d-glv4d (10.101.192.208) -> 35.237.19.94 (35.237.19.94:0)]
❌ command "ping -c 1 -W 2 35.237.19.94" failed: command failed (pod=cilium-test-1/client2-d56fbd75d-glv4d, container=client2): command terminated with exit code 1
Sysdump: cilium-sysdump-20260313-182606.zip
It's unclear why KPR would make a different here.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/CIContinuous Integration testing issue or flakeContinuous Integration testing issue or flakearea/kprAnything related to our kube-proxy replacement.Anything related to our kube-proxy replacement.integration/cloudRelated to integration with cloud environments such as AKS, EKS, GKE, etc.Related to integration with cloud environments such as AKS, EKS, GKE, etc.