I noticed that it is possible to have a pretty in depth view into the k8s cluster running on GKE via Stackdriver. How does this differ from deploying Istio in GKE clusters? Does Istio provide more detailed information that Stackdriver is not able to do so?
Stackdriver is used for logging/service monitoring which provides performance and diagnostics data in Kubernetes whereas Istio is a Service Mesh.
Service Monitoring in an opinionated infrastructure helps monitor how end users perceive the systems thereby drill down to the infrastructure level whenever necessary.
Useful Context about StackDriver from Google, with Stackdriver Service Monitoring, you get the answers to the following questions:
However, when it comes to Istio:
Stackdriver is the default logging solution for clusters deployed on Google Kubernetes Engine.
In simple terms, Stack driver brings logging, monitoring and diagnostics and Istio, the service mesh does the actual implementation of what all should be done and how.