<p>I have setup a Kubernetes cluster (on GKE). Running multiple services but mainly serving a webapp through a stock Ingress controller.</p>

<p>Are there any benefits to running a reverse proxy behind the Ingress? The TLS is terminated at this point, so it's not for that. Maybe for some server hardening?</p>

<p>The only advantage of chaining GKE ingress and Nginx is ability to use more advanced configuration provided by Nginx.</p>

<p>Currently there are benefits of running your own reverse proxy skipping ingress. Or to use <a href="https://github.com/kubernetes/contrib/tree/master/ingress/controllers/nginx" rel="nofollow">custom ingress controller</a> instead of GKE one. The main benefits of doing this is:</p>

<ul>
<li>Cost saving, each GKE ingress resource costs money.</li>
<li>Advanced routing/config offered by Nginx or other proxy.</li>
<li>Bypasses the current GKE Ingress beta limitations.</li>
</ul>
