4 ms·
> Istio has become infamous among k8s infrastructure staff as being the cause of more problems than any other part of the stack True in my opinion. Its very co
by pm90 3y ago
> Istio has become infamous among k8s infrastructure staff as being the cause of more problems than any other part of the stack
True in my opinion. Its very complicated and the docs are confusing af.
- throwitaway222 3y agoAt my last company the devops guy was installing istio for 2 years before he gave up. K8s by itself was just fine.
- jq-r 3y agoI've attended a talk on Kubecon last year on how one company adopted Istio service mesh. I've lost the guy in the first 10 minutes of the talk as it was so complicated, and decided that service mesh is 100% not going into our k8s clusters. Recently an overly confident security engineer came to us and demanded that we get service mesh because thats a SOX requirement. I have no idea from where these people get pipe dreams like that.
- AlecBG 3y agoI think Istio docs are great! I do agree that it's complicated, and I think their API is more confusing that it needs to be. The ontology of DestinationRules, VirtualServices, ServiceEntrys, Gateways (as in the K8s resource), gateways (as in the istio gateway Helm chart) is not the best.
- rexarex 3y agoThe docs are TERRIBLE once you need to actually use them in prod.