[Suggestion] - Ingress : support multiple path

[j0nathan33]

Suggestion

For my jira instance, I will need to support multiple paths in ingress because I need to redirect some path to another service. This service handle some custom Jira images. Can we support this feature ?

Thank

Product

Jira

Code of Conduct

• I agree to follow this project's Code of Conduct

[bianchi2]

@j0nathan33 could you please elaborate on your use case and how your ideal ingress should look like? Would you benefit from ingress.additionalPaths[]?

[j0nathan33]

Context : Where I work, we have almost the largest number of Jira server instances in the world. In a few months, we target to have 3 jiradc instances and all Jira servers will be archived but available if anyone needs them.

If we have to upload data on each pvc, it will be very complicated and too many errors can occurs (Somebody forgot to modify script when he created new test instance, pvc name/id has changed, etc).

My ideal ingress should look like this :

kind: Ingress
apiVersion: networking.k8s.io/v1
metadata:
  name: jira701
spec:
  ingressClassName: webapprouting.kubernetes.azure.com
  tls:
    - hosts:
        - jira701.u******.org
      secretName: keyvault-jira701
  rules:
    - host: jira701.u******.org
      http:
        paths:
          - path: /jira
            pathType: Prefix
            backend:
              service:
                name: jira701
                port:
                  number: 80
          - path: /jira/uimages
            pathType: Prefix
            backend:
              service:
                name: jira-static-content
                port:
                  number: 80

Main benefit from ingress.additionalPaths:

1. It is easier to maintain on all Jira instances
2. We can't create a new docker image every time, because when we redeploy the node, almost each time, advances roadmap isn't enabled.
3. less downtime for add/remove static content (Some jiradc instance, we have some domain name differences per node and some node isn't HA. This node is only accessible from the Internet and it have some custom firewall rule. Security teams request it)
4. For external node, user has only access to this node. If we point image url to another server directly, user will not see image because external user has only access to 1 node.

[bianchi2]

@j0nathan33 thanks for a detailed explanation. The change looks simple enough to implement (especially since it's on user to define additionalPaths). It'll try and raise a PR next week.