<p>I am new to the whole container-orchestration world and was wondering if the microservices I deploy with Kubernetes need a secure connection too or if the Ingress TLS termination is enough.</p>

<p>For example I have an NGINX microservice with currently no SSL/TLS setup whatsoever. When users communicate with this microservice, the connection is encrypted because I set up an Ingress with TLS termination.</p>

<p>Are there any security drawbacks in such a scenario? I find it very hard to find proper literature regarding this topic.</p>

Alex Gogl
<p>It definitely will work. I mean ingress with TLS termination. It depends on security requirements of your project. If you ok with un-encripted traffic inside your cluster, you can go with it.</p>

<p>Though, if you will be running micro-services in production, the best practice for secure service-to-service communication is <a href="https://istio.io/docs/concepts/security/" rel="nofollow noreferrer">Istio mesh</a> with <a href="https://istio.io/docs/concepts/security/#mutual-tls-authentication" rel="nofollow noreferrer">mutual TLS authentication</a></p>

<p>What it does is injects sidecar proxy (envoy) for each of your services
<a href="https://i.stack.imgur.com/BUt8E.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/BUt8E.png" alt="enter image description here"></a></p>
