<p>I have a few applications hosted on a single <code>Amazon Load Balancer</code>, at different endpoints on the <code>ALB</code> etc. This is server and generated through <code>Kubernetes EKS</code>.</p>
<pre><code>          - path: /*
            backend:
              serviceName: ssl-redirect        
              servicePort: use-annotation
          - path: /a/*
            backend:
              serviceName: service-1
              servicePort: 8080
          - path: /b/*
            backend:
              serviceName: service-2
              servicePort: 8085
</code></pre>
<p>For the <code>/*</code> path, I have it route to a <code>Vue UI</code> application.</p>
<p>This application has a few routes, with client side routing. These routes work fine when done through the <code>UI</code>. I want to be able to link directly to these client side routes through the URL bar, or at least redirect to the root <code>UI</code>. However, when I try to hit it directly, and just route to the <code>UI</code> component in the ingress:</p>
<pre><code>          - path: /path1/*
            backend:
              serviceName: ui
              servicePort: 80
          - path: /path2/*
            backend:
              serviceName: ui
              servicePort: 80
          - path: /*
            backend:
              serviceName: ui
              servicePort: 80
</code></pre>
<p>The regular <code>UI</code> route still works, however <code>/path1</code> and <code>/path2</code> return 404. The other applications in this ingress return fine (<code>/path a</code> and <code>/path b</code>, <code>/service-1</code> and <code>/service-2</code>).</p>

Sheen
<p>Server-side and client side routings are completely different.</p>
<p>You want to make server-side routing. I.e, server-side rules should exist.
Server app doesn't know neither <code>/path1</code> nor <code>/path2</code>. Therefore, you get <code>404</code> from the server.</p>
