<p>I'm using k8s to deploy my app which has 3 parts. The main website (landing page), App component 1 (by admins only) and App Component 2 (for paid users). I've recently come across a pattern where there is a main external load balancer, and an ingress for each part of the app. Eg:</p>

<pre><code>LB 
  -&gt; Ingress1 -&gt; Main App
  -&gt; Ingress2 -&gt; App Component 1 (only accessible by admins)
  -&gt; Ingress3 -&gt; App Component 2 (only accessible by paid users)
</code></pre>

<p>Is it common to have an architecture like this? 
Could someone point me to a few good examples (using k8s) which are deploying apps like this. Thanks in advance!</p>

Panda
<p>The most common way that we can follow is to create a single ingress which will forward a traffic based on path.
For example,</p>

<pre><code>paths:
          - path: /app1/
            backend:
              serviceName: app_1
              servicePort: 80
          - path: /app2/
            backend:
              serviceName: app_2
              servicePort: 80
</code></pre>

<p>So "serviceName" is any service name created in k8s(LB/NodePort/ClusterIP).
Finally use this created ingress in external LB/ App GW to forward your external traffic to your application.</p>
