<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Cilium - Tag - Lorenzo's Blog</title><link>https://www.k8s.it/tags/cilium/</link><description>Cilium - Tag - Lorenzo's Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 11 Aug 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://www.k8s.it/tags/cilium/" rel="self" type="application/rss+xml"/><item><title>Kubernetes Service Mesh</title><link>https://www.k8s.it/posts/kubernetes-servicemesh/</link><pubDate>Tue, 11 Aug 2020 00:00:00 +0000</pubDate><author>Lorenzo Girardi</author><guid>https://www.k8s.it/posts/kubernetes-servicemesh/</guid><description><![CDATA[<div class="featured-image">
                <img src="/images/kubernetes-servicemesh/img_flow.png" referrerpolicy="no-referrer">
            </div><p></p>
<p>Do we need a service mesh? A few years ago I started evaluating this feature for existing infrastructure. There are many concepts to consider, and many mistakes people commonly make in thinking about what service mesh does.</p>
<p>Better to start with what a service mesh is <strong>NOT</strong>.</p>
<h2 id="what-a-service-mesh-is-not">What a Service Mesh Is NOT</h2>
<ul>
<li>Not an API gateway (though they may share some components)</li>
<li>Not the location for firewall rules</li>
<li>Not a magical application performance booster</li>
<li>Not something to add without a clear scope — if you do, it could create disorder</li>
</ul>
<h2 id="what-a-service-mesh-is">What a Service Mesh IS</h2>
<p>The short answer covers four areas:</p>]]></description></item></channel></rss>