github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-22 11:21:47 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #78350 from globervinodhn/hostip_hostport_promote

Browse Source 
Promote existing E2Es for hostport/HostIP resolution to conformance
This commit is contained in:
Kubernetes Prow Robot 2019-07-19 14:25:24 -07:00 committed by GitHub
commit 65b094676f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 16 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
test/conformance/testdata/conformance.txt vendored
View File

@ -213,6 +213,8 @@ test/e2e/node/pre_stop.go: "should call prestop when killing a pod"
test/e2e/scheduling/predicates.go: "validates resource limits of pods that are allowed to run"
test/e2e/scheduling/predicates.go: "validates that NodeSelector is respected if not matching"
test/e2e/scheduling/predicates.go: "validates that NodeSelector is respected if matching"
test/e2e/scheduling/predicates.go: "validates that there is no conflict between pods with same hostPort but different hostIP and protocol"
test/e2e/scheduling/predicates.go: "validates that there exists conflict between pods with same hostPort and protocol but one using 0.0.0.0 hostIP"
test/e2e/storage/empty_dir_wrapper.go: "should not conflict"
test/e2e/storage/empty_dir_wrapper.go: "should not cause race condition when used for configmaps"
test/e2e/storage/subpath.go: "should support subpaths with secret pod"

16
test/e2e/scheduling/predicates.go
View File

@ -562,7 +562,13 @@ var _ = SIGDescribe("SchedulerPredicates [Serial]", func() {
verifyResult(cs, 1, 0, ns)
})
ginkgo.It("validates that there is no conflict between pods with same hostPort but different hostIP and protocol", func() {
/*
Release : v1.16
Testname: Scheduling, HostPort matching and HostIP and Protocol not-matching
Description: Pods with the same HostPort value MUST be able to be scheduled to the same node
if the HostIP or Protocol is different.
*/
framework.ConformanceIt("validates that there is no conflict between pods with same hostPort but different hostIP and protocol", func() {
nodeName := GetNodeThatCanRunPod(f)
@ -589,7 +595,13 @@ var _ = SIGDescribe("SchedulerPredicates [Serial]", func() {
createHostPortPodOnNode(f, "pod3", ns, "127.0.0.2", port, v1.ProtocolUDP, nodeSelector, true)
})
ginkgo.It("validates that there exists conflict between pods with same hostPort and protocol but one using 0.0.0.0 hostIP", func() {
/*
Release : v1.16
Testname: Scheduling, HostPort and Protocol match, HostIPs different but one is default HostIP (0.0.0.0)
Description: Pods with the same HostPort and Protocol, but different HostIPs, MUST NOT schedule to the
same node if one of those IPs is the default HostIP of 0.0.0.0, which represents all IPs on the host.
*/
framework.ConformanceIt("validates that there exists conflict between pods with same hostPort and protocol but one using 0.0.0.0 hostIP", func() {
nodeName := GetNodeThatCanRunPod(f)
// use nodeSelector to make sure the testing pods get assigned on the same node to explicitly verify there exists conflict or not