Skip to content

CI: ClusterMesh: timeouts in client-egress-l7 #24990

@pchaigno

Description

@pchaigno

I've seen a few variations of this, all with L7 on egress and clustermesh:

  ❌ client-egress-l7-named-port/pod-to-pod/curl-1: cilium-test/client2-bc59f56d5-w5w9c (10.242.1.182) -> cilium-test/echo-other-node-5c58b8cf8b-g4lwr (10.244.1.197:8080)
  ❌ client-egress-l7/pod-to-world/http-to-google.com-0: cilium-test/client2-bc59f56d5-bzr5n (10.242.1.229) -> google.com-http (google.com:80)
  ❌ client-egress-l7/pod-to-world/http-to-google.com-0: cilium-test/client2-bc59f56d5-qkj62 (10.242.1.156) -> google.com-http (google.com:80)

Link: https://github.com/cilium/cilium/actions/runs/4722694005/jobs/8377638774
Sysdump:
cilium-sysdumps-5.zip

Link: https://github.com/cilium/cilium/actions/runs/4719364276/jobs/8370097019
Sysdump:
cilium-sysdumps-1.zip

Link: https://github.com/cilium/cilium/actions/runs/4713940509/jobs/8359970494
Sysdump:
cilium-sysdumps-2.zip

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/CIContinuous Integration testing issue or flakearea/clustermeshRelates to multi-cluster routing functionality in Cilium.area/proxyImpacts proxy components, including DNS, Kafka, Envoy and/or XDS servers.ci/flakeThis is a known failure that occurs in the tree. Please investigate me!staleThe stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions