github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-09-19 17:16:12 +00:00
Code Issues Projects Releases Wiki Activity

move e2e hostport conflict test to sig-network

Browse Source 
The test "validates that there is no conflict between pods with same
hostPort but different hostIP and protocol" was testing the scheduler
capability to schedule pods on the same node with hostPorts, however,
it wasn´t validating that the HostPorts was working, causing false
positives, because the pods were scheduled, but the HostPort exposed
wasn´t working.

In order to test the HostPort functionality, we have to use HostNetwork
pods, that are incompatible with Windows platforms. Also, since this
is touching both network and scheduling, there is no clear the ownership,
but sig-network is happy to adopt it.

We also add a new test for scheduling only under "scheduling", so Windows
folks can use it to test the scheduled in that platform.
This commit is contained in:
Antonio Ojea
2021-01-22 09:31:49 +01:00
parent cea1098997
commit 08a8e80c9f
4 changed files with 210 additions and 78 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
test/conformance/testdata/conformance.yaml vendored
View File

@@ -1621,6 +1621,14 @@
DNS configuration MUST be configured in the Pod.
release: v1.17
file: test/e2e/network/dns.go
- testname: Scheduling, HostPort matching and HostIP and Protocol not-matching
codename: '[sig-network] HostPort validates that there is no conflict between pods
with same hostPort but different hostIP and protocol [LinuxOnly] [Conformance]'
description: Pods with the same HostPort value MUST be able to be scheduled to the
same node if the HostIP or Protocol is different. This test is marked LinuxOnly
since hostNetwork is not supported on Windows.
release: v1.16, v1.20
file: test/e2e/network/hostport.go
- testname: Ingress API
codename: '[sig-network] Ingress API should support creating Ingress API operations
[Conformance]'
@@ -2030,15 +2038,6 @@
which represents all IPs on the host.
release: v1.16
file: test/e2e/scheduling/predicates.go
- testname: Scheduling, HostPort matching and HostIP and Protocol not-matching
codename: '[sig-scheduling] SchedulerPredicates [Serial] validates that there is
no conflict between pods with same hostPort but different hostIP and protocol
[LinuxOnly] [Conformance]'
description: Pods with the same HostPort value MUST be able to be scheduled to the
same node if the HostIP or Protocol is different. This test is marked LinuxOnly
since hostNetwork is not supported on Windows.
release: v1.16
file: test/e2e/scheduling/predicates.go
- testname: Pod preemption verification
codename: '[sig-scheduling] SchedulerPreemption [Serial] PreemptionExecutionPath
runs ReplicaSets to verify preemption running path [Conformance]'