08a8e80c9f
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. |
||
|---|---|---|
| .. | ||
| testdata | ||
| BUILD | ||
| cf_header.md | ||
| conformance_test.sh | ||
| doc.go | ||
| OWNERS | ||
| README.md | ||
| walk_test.go | ||
| walk.go | ||
This directory contains the regression test for controlling the list of all conformance tests.
If you add or remove a conformance test, this test will fail and you will need
to update the golden list of tests stored in testdata/. Changes to that file
require review by sig-architecture.
To update the list, run
bazel build //test/conformance:list_conformance_tests
cp bazel-bin/test/conformance/conformance.yaml test/conformance/testdata
Add the changed file to your PR, then send for review.