title: app on path instead of root not working for Kubernetes Ingress
body: <p>I have an issue at work with K8s Ingress and I will use fake examples here to illustrate my point.
  Assume I have an app called Tweeta and my company is called ABC. My app currently sits on tweeta.abc.com.
  But we want to migrate our app to app.abc.com/tweeta.</p>
  <p>My current ingress in K8s is as belows:</p>
  <pre><code>apiVersion: networking.k8s.io/v1beta1
  kind: Ingress
  metadata:
    name: tweeta-ingress
  spec:
    rules:
    - host: tweeta.abc.com
      http:
        paths:
        - path: /
          backend:
            serviceName: tweeta-frontend
            servicePort: 80
        - path: /api
          backend:
            serviceName: tweeta-backend
            servicePort: 80
  </code></pre>
  <p>For migration, I added a second ingress:</p>
  <pre><code>apiVersion: networking.k8s.io/v1beta1
  kind: Ingress
  metadata:
    name: tweeta-ingress-v2
  spec:
    rules:
    - host: app.abc.com
      http:
        paths:
        - path: /tweeta
          backend:
            serviceName: tweeta-frontend
            servicePort: 80
        - path: /tweeta/api
          backend:
            serviceName: tweeta-backend
            servicePort: 80
  
  </code></pre>
  <p>For sake of continuity, I would like to have 2 ingresses pointing to my services at the same time. When the new domain is ready and working, I would just need to tear down the old ingress.</p>
  <p>However, I am not getting any luck with the new domain with this ingress. Is it because it is hosted on a path and the k8s ingress needs to host on root? Or is it a configuration I would need to do on the nginx side?</p>