Skip to content

Migrate K8sDatapathServicesTest to newer testing infrastructure #44168

@joestringer

Description

@joestringer

Migrate K8sDatapathServicesTest 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 K8sDatapathServicesTest | grep -v cliFocus
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks N/S loadbalancing ClusterIP cannot be accessed externally when access is disabled
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks N/S loadbalancing Supports IPv4 fragments
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks N/S loadbalancing Tests with TC, direct routing and dsr with geneve
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks N/S loadbalancing Tests with TC, direct routing and Hybrid-DSR with Geneve
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks N/S loadbalancing Tests with TC, geneve tunnel, and Hybrid-DSR with Geneve
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks N/S loadbalancing Tests with TC, direct routing and Hybrid
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks N/S loadbalancing Tests with TC, geneve tunnel, dsr and Maglev
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks N/S loadbalancing Tests externalIPs
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks N/S loadbalancing Tests GH#10983
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks N/S loadbalancing Tests NodePort with sessionAffinity from outside
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks N/S loadbalancing Tests security id propagation in N/S LB requests fwd-ed over tunnel
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks N/S loadbalancing Tests with XDP, direct routing, DSR and Maglev
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks N/S loadbalancing Tests with XDP, direct routing, DSR and Random
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks N/S loadbalancing Tests with XDP, direct routing, DSR with Geneve and Maglev
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks N/S loadbalancing Tests with XDP, direct routing, Hybrid and Maglev
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks N/S loadbalancing Tests with XDP, direct routing, Hybrid and Random
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks N/S loadbalancing Tests with XDP, direct routing, SNAT and Maglev
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks N/S loadbalancing With ClusterIP external access ClusterIP can be accessed when external access is enabled
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks N/S loadbalancing With host policy Tests NodePort
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks device reconfiguration Detects newly added device and reloads datapath
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks E/W loadbalancing (ClusterIP, NodePort from inside cluster, etc) Checks in-cluster KPR Tests HealthCheckNodePort
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks E/W loadbalancing (ClusterIP, NodePort from inside cluster, etc) Checks in-cluster KPR Tests that binding to NodePort port fails
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks E/W loadbalancing (ClusterIP, NodePort from inside cluster, etc) Checks in-cluster KPR with L7 policy Tests NodePort with L7 Policy
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks E/W loadbalancing (ClusterIP, NodePort from inside cluster, etc) Checks service accessing itself (hairpin flow)
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks E/W loadbalancing (ClusterIP, NodePort from inside cluster, etc) TFTP with DNS Proxy port collision Tests TFTP from DNS Proxy Port
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks E/W loadbalancing (ClusterIP, NodePort from inside cluster, etc) with L4 policy Tests NodePort with L4 Policy
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks E/W loadbalancing (ClusterIP, NodePort from inside cluster, etc) with L7 policy Tests NodePort with L7 Policy
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks E/W loadbalancing (ClusterIP, NodePort from inside cluster, etc) Tests NodePort inside cluster (kube-proxy) vanilla
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks E/W loadbalancing (ClusterIP, NodePort from inside cluster, etc) Tests NodePort inside cluster (kube-proxy) with externalTrafficPolicy=Local
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks E/W loadbalancing (ClusterIP, NodePort from inside cluster, etc) Tests NodePort inside cluster (kube-proxy) with IPSec and externalTrafficPolicy=Local
.github/actions/ginkgo/main-focus.yaml:  # K8sDatapathServicesTest Checks E/W loadbalancing (ClusterIP, NodePort from inside cluster, etc) Tests NodePort inside cluster (kube-proxy) with the host firewall and externalTrafficPolicy=Local
test/ginkgo-ext/junit_reporter.go:	// Look for test class patterns like "K8sAgentPolicyTest", "K8sDatapathServicesTest", etc.
test/ginkgo-ext/junit_reporter.go:	case "K8sDatapathServicesTest":
test/k8s/services.go:var _ = SkipDescribeIf(helpers.RunsOn54Kernel, "K8sDatapathServicesTest", func() {

Related: #37837

Metadata

Metadata

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