<p>Recently I have built several microservices within a k8s cluster with Nginx ingress controller and they are working normally.</p>
<p>When dealing with communications among microservices, I attempted gRPC and it worked. Then I discover when microservice A -&gt; gRPC -&gt; microservice B, all requests were only occurred at 1 pod of microservice B (e.g. total 10 pods available for microservice B). In order to load balance the requests to all pods of microservice B, I attempted linkerd and it worked. However, I realized gRPC sometimes will produce internal error (e.g. 1 error out of 100 requests), making me changed to using the k8s DNS way (e.g. my-svc.my-namespace.svc.cluster-domain.example). Then, the requests never fail. I started to hold up gRPC and linkerd.</p>
<p>Later, I was interested in istio. I successfully deployed it to the cluster. However, I observe it always creates its own load balancer, which is not so matching with the existing Nginx ingress controller.</p>
<p>Furthermore, I attempted prometheus and grafana, as well as k9s. These tools let me have better understanding on cpu and memory usage of the pods.</p>
<p>Here I have several questions that I wish to understand:-</p>
<ol>
<li>If I need to monitor cluster resources, we have prometheus, grafana and k9s. Are they doing the same monitoring role as service mesh (e.g. linkerd, istio)?</li>
<li>if k8s DNS can already achieve load balancing, do we still need service mesh?</li>
<li>if using k8s without service mesh, is it lag behind the normal practice?</li>
</ol>
<p>Actually I also want to use service mesh every day.</p>

<p>The simple answer is</p>
<blockquote>
<p>Service mesh for a kubernetes server is not necessary</p>
</blockquote>
<p>Now to answer your questions</p>
<blockquote>
<p>If I need to monitor cluster resources, we have prometheus, grafana and k9s. Are they doing the same monitoring role as service mesh (e.g. linkerd, istio)?</p>
</blockquote>
<p>K9s is a cli tool that is just a replacement to the <code>kubectl</code> cli tool. It is not a monitor tool. Prometheus and grafana are monitoring tools that will need use the data provided by applications(pods) and builds the time-series data which can be visualized as charts, graphs etc. However the applications have to provide the monitoring data to Prometheus. Service meshes may use a sidecar and provide some default metrics useful for monitoring such as <code>number of requests handled in a second</code>. Your application doesn't need to have any knowledge or implementation of the metrics. Thus service meshes are optional and it offloads the common things such as monitoring or authorization.</p>
<blockquote>
<p>if k8s DNS can already achieve load balancing, do we still need service mesh?</p>
</blockquote>
<p>Service meshes are not needed for load balancing. When you have multiple services running in the cluster and want to use a single entry point for all your services to simplify maintenance and to save cost, Ingress controllers such as Nginx, Traefik, HAProxy are used. Also, service meshes such as Istio comes with its own ingress controller.</p>
<blockquote>
<p>if using k8s without service mesh, is it lag behind the normal practice?</p>
</blockquote>
<p>No, there can be clusters that don't have service meshes today and still use Kubernetes.</p>
<p>In the future, Kubernetes may bring some functionalities from service meshes.</p>
