Skip to content

[Failing Test] [sig-network] Kubernetes e2e suite.[It] [sig-network] LoadBalancers [Feature:LoadBalancer] should not have connectivity disruption during rolling update with externalTrafficPolicy=Local [Slow] #132161

Open
@elieser1101

Description

@elieser1101

Which jobs are failing?

master-blocking

  • gci-gce-ingress

Which tests are failing?

Kubernetes e2e suite.[It] [sig-network] LoadBalancers [Feature:LoadBalancer] should not have connectivity disruption during rolling update with externalTrafficPolicy=Local [Slow]

Since when has it been failing?

6/4/2025, 9:53:01 PM
6/5/2025, 9:54:02 AM
6/6/2025, 3:54:02 AM
6/6/2025, 9:54:02 AM

Testgrid link

https://testgrid.k8s.io/sig-release-master-blocking#gci-gce-ingress

Reason for failure (if possible)

{ failed [FAILED] Encountered too many errors when doing HTTP requests to the load balancer address. Success rate is 94.17%, and the minimum allowed threshold is 95.00%.
In [It] at: k8s.io/kubernetes/test/e2e/network/loadbalancer.go:1438 @ 06/06/25 19:37:17.431
}

Anything else we need to know?

No response

Relevant SIG(s)

/sig network
cc @kubernetes/release-team-release-signal

Metadata

Metadata

Assignees

Labels

kind/failing-testCategorizes issue or PR as related to a consistently or frequently failing test.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.sig/networkCategorizes an issue or PR as relevant to SIG Network.

Type

No type

Projects

Status

FLAKY

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions