expected failure for sessionaffinity with different ports

K8sbykeshed / k8s-service-validator

Kubernetes Network Service Validator

22 stars 10 forks source link

expected failure for sessionaffinity with different ports #89

Closed knabben closed 2 years ago

knabben commented 2 years ago

We should refactor the test "should always reach to same pod, even with via different protocol", so only session affinity across hosts are expected, not ports, since this is not implemented/guaranteed in any proxy.

For now skipping the test, so the CI can have the control job (kproxy iptables) passing.

@yzaccc

yzaccc commented 2 years ago

return "?" for the result of the test(not to fail the pipeline), as the test is expected to fail currently.