Ability to serve webapps with rewrite target under subpaths while appending slashes

[simhnna]

The following is an ingress from the docs with an added rewrite rule to append a slash

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    nginx.ingress.kubernetes.io/use-regex: "true"
    nginx.ingress.kubernetes.io/rewrite-target: /$2
    nginx.ingress.kubernetes.io/configuration-snippet: |
      rewrite ^(/something)$ " $1/" permanent;
  name: rewrite
  namespace: default
spec:
  ingressClassName: nginx
  rules:
  - host: rewrite.bar.com
    http:
      paths:
      - path: /something(/|$)(.*)
        pathType: ImplementationSpecific
        backend:
          service:
            name: http-svc
            port: 
              number: 80

The ingress can be summarized as following:

• serve webapp under /something/
• redirect /something to /something/
• rewrite target stripping /something

We're currently in the process of phasing out configuration-snippet but we don't know how to best accomplish the combination of the three points above.

• We're fine with having ImplementationSpecific paths, so something like http://nginx.ingress.kubernetes.io/app-root that works for all paths would be ok
• If we can somehow strip the prefix while using Prefix paths even better (they should autoredirect appending the slash out of the box)
• We could do the redirect in our own applications, but we can't do that for third party software
• We'd like to avoid declaring duplicate ingresses that redirect appending slashes

Note: I've posted about this in slack but didn't get a solution there (yet)

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[github-actions]

This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach #ingress-nginx-dev on Kubernetes Slack.