Skip to content

Failures in [sig-network] Network should set TCP CLOSE_WAIT timeout and Services should be rejected when no endpoints exist #10002

New issue
New issue
Closed
#28157
Closed
Failures in [sig-network] Network should set TCP CLOSE_WAIT timeout and Services should be rejected when no endpoints exist#10002
#28157
Labels
area/datapathImpacts bpf/ or low-level forwarding details, including map management and monitor messages.kind/bugThis is a bug in the Cilium logic.kind/community-reportThis was reported by a user in the Cilium community, eg via Slack.need-more-infoMore information is required to further debug or fix the issue.pinnedThese issues are not marked stale by our issue bot.
@hakman

Description

@hakman
hakman
opened on Jan 30, 2020

Support

We are adding e2e tests to the Kops project for most Kubernetes network plugins, Cilium included. Seems that some of the tests are failing and wanted to get some feedback here about them.
https://testgrid.k8s.io/sig-cluster-lifecycle-kops#kops-aws-cni-cilium

The tests that fail are:

[sig-network] Network should set TCP CLOSE_WAIT timeout
[sig-network] Services should be rejected when no endpoints exist

Would like to know if there are any settings to make these pass or if there is any plan to fix them. Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/datapathImpacts bpf/ or low-level forwarding details, including map management and monitor messages.kind/bugThis is a bug in the Cilium logic.kind/community-reportThis was reported by a user in the Cilium community, eg via Slack.need-more-infoMore information is required to further debug or fix the issue.pinnedThese issues are not marked stale by our issue bot.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions