d5b7ef86bb
The e2e test, included as part of Conformance, "validates that there is no conflict between pods with same hostPort but different hostIP and protocol" was only testing that the pods were scheduled without conflict but was never testing the functionality. The test should check that pods with containers forwarding the same hostPort can be scheduled without conflict, and that those exposed HostPort are forwarding the ports to the corresponding pods. the predicate tests were using loopback addresses for the the hostPort test, however, those have different semantics depending on the IP family, i.e. you can not bind to ::1 and ::2 simultanously, in addition, IP forwarding from localhost to localhost in IPv6 is not working since it doesn't have the kernel route_localnet hack. |
||
|---|---|---|
| .. | ||
| BUILD | ||
| events.go | ||
| framework.go | ||
| limit_range.go | ||
| nvidia-gpus.go | ||
| OWNERS | ||
| predicates.go | ||
| preemption.go | ||
| priorities.go | ||
| ubernetes_lite_volumes.go | ||
| ubernetes_lite.go | ||