Menu
Back to Discussions

when do u think its time to add a service mesh tho

were running a growing number of microservices in Kubernetes, and managing inter-service communication, security, and observability is getting complex. Things like mTLS, retries, and tracing are being implemented inconsistently across services. I'm starting to wonder if a service mesh like Istio or Linkerd might be the next logical step. For those who have adopted a service mesh, what was the tipping point for you? What specific problems did it solve, and were there any unexpected downsides or complexities
24 comments

Comments

Loading comments...