test: Fix kube-proxy-free on GKE due to wrong k8sServiceHost value
test: Fix kube-proxy-free on GKE due to wrong k8sServiceHost value

On GKE, kube-apiserver doesn't run on the first node as in our Jenkins
builds, leading to a failure to start Cilium in kube-proxy-free mode.
Since kube-proxy is always provisioned on GKE, we don't need to specify
k8sServiceHost and k8sServicePort on GKE.

Reported-by: Gilberto Bertin <e45dca12016e9fd4d68d2c7903502c5e1a1f4f1b@isovalent.com>
Suggested-by: Martynas Pumputis <6b0d31c0d563223024da45691584643ac78c96e8@lambda.lt>
Signed-off-by: Paul Chaignon <a027184a55211cd23e3f3094f1fdc728df5e0500@cilium.io>

tgraf/cilium,tklauser/cilium,tgraf/cilium,cilium/cilium,tgraf/cilium,tgraf/cilium,michi-covalent/cilium,tklauser/cilium,cilium/cilium,tgraf/cilium,tgraf/cilium,michi-covalent/cilium,tklauser/cilium,cilium/cilium,tklauser/cilium,michi-covalent/cilium,michi-covalent/cilium,cilium/cilium,tklauser/cilium,michi-covalent/cilium,cilium/cilium