<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>olafmol</author><text>Istio adds to Kubernetes:&lt;p&gt;- Automatic load balancing for HTTP, gRPC, WebSockets, and TCP traffic.&lt;p&gt;- Fine-grained control of traffic behaviour with rich routing rules, retries, fail-overs, and fault injection.&lt;p&gt;- A pluggable policy layer and configuration API supporting access controls, rate limits and quotas.&lt;p&gt;- Automatic metrics, logs, and traces for all traffic within a cluster, including cluster ingress and egress.&lt;p&gt;- Secure service-to-service communication in a cluster with strong identity-based authentication and authorization.&lt;p&gt;Istio on its own is powerful and flexible. It can also be hard to understand, setup, and manage, plus can be brittle.&lt;p&gt;(disclaimer: I&amp;#x27;m co-founder of Vamp.io, a canary test &amp;amp; release system for DevOps teams that works with both HAProxy and Istio)&lt;p&gt;What Istio imho misses is a user-friendly way of setting up, managing and automating Istio configurations for microservices topologies to quickly achieve automated canary-releasing and A&amp;#x2F;B testing pipelines. Call Vamp a canary-releasing and A&amp;#x2F;B testing “control plane” for Istio&amp;#x2F;K8s if you will.&lt;p&gt;Basically the potential of service-meshes like Istio lies in &amp;quot;driving&amp;quot; it from higher-level metric&amp;#x2F;KPI-based automation systems.&lt;p&gt;We wrote several blog-posts on how to make use of Istio, starting here: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;medium.com&amp;#x2F;vamp-io&amp;#x2F;taming-istio-76fab339f685&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;medium.com&amp;#x2F;vamp-io&amp;#x2F;taming-istio-76fab339f685&lt;/a&gt; (more blogs on Istio can be found here &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;medium.com&amp;#x2F;vamp-io&amp;#x2F;tagged&amp;#x2F;istio&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;medium.com&amp;#x2F;vamp-io&amp;#x2F;tagged&amp;#x2F;istio&lt;/a&gt;)&lt;p&gt;Hopefully this gives some more insights in what Istio is, what it isn&amp;#x27;t, and how you can leverage it in your pipelines and architectures.</text><parent_chain></parent_chain></comment><story><title>Istio – An open platform to connect, manage, and secure microservices</title><url>https://github.com/istio/istio</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>altmind</author><text>Can somebody explain what istio does in simple words?&lt;p&gt;I see that it hooks into micro&amp;#x2F;services communication, but why do we need that? isnt policies enforced by cni plugins? and can microservices communicate already with k8s and mesos default setups?&lt;p&gt;is istio an network abstraction layer for k8s and mesos? why would anyone want that, is there anybody who changes scheduling runtimes often?</text><parent_chain></parent_chain></comment><story><title>Istio – An open platform to connect, manage, and secure microservices</title><url>https://github.com/istio/istio</url></story>