This jives pretty well with my (admittedly little) experience with Istio. It's certainly frustrating at times, but I still find the documentation is actually pr

This jives pretty well with my (admittedly little) experience with Istio. It's certainly frustrating at times, but I still find the documentation is actually pretty decent. It's just that everything seems to lead down a rabbit hole. But this, I think, is just a Kubernetes thing in general. I had the same experience they did with a monitoring stack. But that's because you have to ramp up on some many additional technologies (Prometheus, Grafana, Kiali, etc...). And not just ramp up on their usage, but how they work, interact, and are configured. For Prometheus, for example, they suggest using a federated setup, which adds additional complexeties. I messed around with strict mTLS for quite some time before simply giving up - it just wasn't worth the time sink. But in general I agree with the conclusions. Most things are pretty straight-forward and the documentation has really good examples (using their "Bookinfo" project). It's just the "going off the beaten path" thing they describe when things become difficult.