Re:K8s Service Meshes: The Bill Comes Due
by throwitaway222 on Saturday March 02, 2024 @02:14AM
(#39570592)
At my last company the devops guy was installing istio for 2 years before he gave up. K8s by itself was just fine.
I'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.
I 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.
True in my opinion. Its very complicated and the docs are confusing af.