Skip to content

Migrate K8sDatapathBandwidthTest to newer testing infrastructure #44165

@joestringer

Description

@joestringer

Migrate K8sDatapathBandwidthTest to newer testing infrastructure

These tests should be removed from the test/k8s suite and replaced with either component-based testing (preferred) or end-to-end tests via cilium-cli:

$ git grep K8sDatapathBandwidthTest | grep -v cliFocus
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathBandwidthTest Checks Bandwidth Rate-Limiting Checks Pod to Pod bandwidth, direct routing
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathBandwidthTest Checks Bandwidth Rate-Limiting Checks Pod to Pod bandwidth, geneve tunneling
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathBandwidthTest Checks Bandwidth Rate-Limiting Checks Pod to Pod bandwidth, vxlan tunneling
test/ginkgo-ext/junit_reporter.go:	case "K8sDatapathBandwidthTest":
test/k8s/bandwidth.go:var _ = SkipDescribeIf(helpers.DoesNotRunOnNetNextKernel, "K8sDatapathBandwidthTest", func() {

Related: #37837

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/CI-improvementTopic or proposal to improve the Continuous Integration workflowarea/datapathImpacts bpf/ or low-level forwarding details, including map management and monitor messages.help-wantedYou can help! Post a detailed plan on the issue or create a PR to solve this issue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions