<p>This is more of a design architectural decision to rollout Istio Service Mesh solution into Production. What are the key design decisions to make in this regard. What were the learnings/outcomes after rolling out into Prod. We are considering using Istio Operator as the way to go which would reconcile the state of the service mesh and possibly it would be a service mesh on boarding different k8s(v1.13.12) clusters gradually.</p>

Avi
<p>Istio announced that <a href="https://istio.io/news/releases/1.0.x/announcing-1.0/" rel="nofollow noreferrer">version 1.0 is production-ready</a>. Here are some links about the design/architectural decisions to deploy istio in production:</p>

<ul>
<li><a href="https://istio.io/blog/2019/performance-best-practices/" rel="nofollow noreferrer">Benchmarking istio in production</a></li>
<li><a href="https://istio.io/docs/ops/best-practices/" rel="nofollow noreferrer">Istio best practices</a></li>
<li><a href="https://istio.io/docs/ops/deployment/deployment-models/" rel="nofollow noreferrer">Istio deployment models</a></li>
<li><a href="https://istio.io/docs/ops/deployment/performance-and-scalability/" rel="nofollow noreferrer">Performance and scalability in production</a></li>
<li><a href="https://istio.io/about/feature-stages/" rel="nofollow noreferrer">Istio feature status</a> about alpha/beta/stable or production-ready istio features</li>
</ul>

<p><a href="https://github.com/istio/operator" rel="nofollow noreferrer">Here</a> is istio operator and a GitHub <a href="https://github.com/istio/istio/issues/15582" rel="nofollow noreferrer">issue about istio's production/HA docs</a>.</p>
