test: Skip Istio test on k8s <1.17

[jrajahalme]

Istio 1.10 requires at least k8s version 1.17.

Signed-off-by: Jarno Rajahalme jarno@isovalent.com

[jrajahalme]

test-me-please

Job 'Cilium-PR-K8s-GKE' failed and has not been observed before, so may be related to your PR:

Click to show.

Test Name

K8sBookInfoDemoTest Bookinfo Demo Tests bookinfo demo

Failure Output

FAIL: Pods are not ready after timeout

If it is a flake, comment /mlh new-flake Cilium-PR-K8s-GKE so I can create a new GitHub issue to track it.

Job 'Cilium-PR-K8s-1.16-net-next' failed and has not been observed before, so may be related to your PR:

Click to show.

Test Name

K8sKafkaPolicyTest Kafka Policy Tests KafkaPolicies

Failure Output

FAIL: DNS entry of kafka-service is not ready after timeout

If it is a flake, comment /mlh new-flake Cilium-PR-K8s-1.16-net-next so I can create a new GitHub issue to track it.

[pchaigno]

• gke-stable failed with known flake CI: gke-stable (test-gke): Pods are not ready in time: connection refused #17307.
• k8s-1.16-kernel-netnext failed with known flake k8s-1.13-net-next CI: DNS entry is not ready after timeout #14598.
• k8s-1.21-kernel-4.9 failed with known flake CI: K8sPolicyTest: Zero exit code despite curl timeout #15724 and an unknown flake. I filed CI: K8sPolicyTest Basic Test Denies traffic with k8s default-deny ingress-egress policy #17466 for the unknown.

Given all test failures are clearly unrelated (not even the changed test) and reviews are in, I'm marking ready to merge. This PR is to fix a test failure, so an exception to the zero-flake strategy.