gke service mesh istio is slightly different than the ones you deployed it separately
GKE service mesh uses istio but it is not the typical istio that you get out of the box. No pod in istio-system For one, there's no pod running in the istio-system namespace (namespace exist but no pods) And when you do a kubectl get controlplanerevision -n istio-system You will get this - asm-managed Annotation is different In order to ensure that sidecar are automatically injected in your pod, we do require this annotation to be added to our namespace and we have to remove the old label that contains "istio-injection" kubectl label namespace test istio.io/rev=asm-managed --overwrite Gateway deploy manually There's no default load balancer or gateway that will be deployed when you enable service mesh. For that you have to do it manually. To do that you will need to: kubectl create namespace istio-ingress kubectl label namespace istio-ingress istio.io/rev=asm-managed --overwrite And then deploy the instance using the following yaml kubectl...