<p>I have the following ingress resource for one of my apps</p>

<pre><code>apiVersion: extensions/v1beta1
  kind: Ingress
  metadata:
    name:""
    annotations:
      ingress.kubernetes.io..
  spec:
    rules:
    - host: my-app
      http:
        paths:
        - path: /path/to/service
          backend:
            serviceName: my-service
            servicePort: 80
</code></pre>

<p>This works as expected and I can access my service at <code>http://my-app/path/to/service</code>. However the service in my app takes query parameters that dont seem to correctly get redirected for eg:</p>

<pre><code>http://my-app/path/to/service/more/paths
</code></pre>

<p>This brings me back to <code>http://my-app/path/to/service</code></p>

<p>How can I maintain this path structure ?</p>

<p>I believe you need to use wildcards on your path:</p>

<pre><code>apiVersion: extensions/v1beta1
  kind: Ingress
  metadata:
    name:""
    annotations:
      ingress.kubernetes.io..
  spec:
    rules:
    - host: my-app
      http:
        paths:
        - path: /path/to/service/*
          backend:
            serviceName: my-service
            servicePort: 80
</code></pre>

<p>More information <a href="https://github.com/kubernetes/ingress-nginx/issues/1120" rel="nofollow noreferrer">here</a>. Seems like it's hard to find any docs with wildcard examples. Not that this is specific to nginx, it may not work with other ingress controllers.</p>
