test-backport-1.8

Failing istio test leaves istio-proxy injection behind and then causes remaining tests also using the default namespace to fail as they are running istio-proxy sidecar without anyone configuring it. The fail in the Istio test seems strange to me, this is from running cilium-istioctl install, which execs kubectl:

	 2021-04-16T08:23:19.537608Z	error	installer	error running kubectl: exit status 1
	 ✘ Finished applying manifest for component IngressGateways.
	 
	 Component IngressGateways - manifest apply returned the following errors:
	 Error: error running kubectl: exit status 1
	 
	 Error detail:
	 
	 error: error retrieving RESTMappings to prune: invalid resource networking.k8s.io/v1, Kind=Ingress, Namespaced=true: no matches for kind "Ingress" in version "networking.k8s.io/v1" (repeated 1 times)

	 error: error retrieving RESTMappings to prune: invalid resource networking.k8s.io/v1, Kind=Ingress, Namespaced=true: no matches for kind "Ingress" in version "networking.k8s.io/v1" (repeated 1 times)

Found this for reference, but don't yet understand what is going on: kubernetes/kubernetes#90077.
Maybe our test VMs have too new kubectl (1.19?), which then tries to use networking.k8s.io/v1 when it should use networking.k8s.io/v1beta1 for k8s < 1.19??

Maybe @aanm would know something about this?

@aanm I see the same k8s problem also in earlier builds on v1.8, so this is not caused by this PR. It seems to me that we have at some point updated the test environment to use kubectl version that is incompatible with k8s versions < 1.19??

E.g.: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.14-kernel-4.9/183/

test-backport-1.8