1687916844
During the September 29th, 2022 SIG-Network meeting we decided to demote the two affinity timeout conformance tests. This was because: (a) there is no documented correct behavior for these tests other than "what kube-proxy does" (b) even the kube-proxy behavior differs depending on the backend implementation of iptables, IPVS, or [win]userspace (and winkernel doesn't at all) (c) iptables uses only srcip matching, while userspace and IPVS use srcip+srcport (d) IPVS and iptables have different minimum timeouts and we had to hack up the test itself to make IPVS pass (e) popular 3rd party network plugins also vary in their implementation Our plan is to deprecate the current affinity options and re-add specific options for various behaviors so it's clear exactly what plugins support and which behavior (if any) we want to require for conformance in the future. Signed-off-by: Dan Williams <dcbw@redhat.com> |
||
|---|---|---|
| .. | ||
| image | ||
| testdata | ||
| cf_header.md | ||
| conformance_test.sh | ||
| doc.go | ||
| gen-conformance-docs.sh | ||
| gen-conformance-yaml.sh | ||
| gen-specsummaries.sh | ||
| OWNERS | ||
| README.md | ||
| spec-to-docs.sh | ||
| spec-to-yaml.sh | ||
| 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 hack/update-conformance-yaml.sh
Add the changed file to your PR, then send for review.