[Bug] Running jaeger with custom ingress behind an application gateway

[sanasz91mdev]

What happened?

jaeger ingress does not work with custom path

Steps to reproduce

1- Create an application gateway with backend pointing to IP of load balancer provisioned by ingress
2- configure the /jaeger rule in application gateway
3- create an ingress as below:

kind: Ingress
apiVersion: networking.k8s.io/v1
metadata:
  labels:
    app: jaeger
    app.kubernetes.io/component: query-ingress
    app.kubernetes.io/instance: prod-jaeger-es
    app.kubernetes.io/managed-by: jaeger-operator
    app.kubernetes.io/name: prod-jaeger-es-query
    app.kubernetes.io/part-of: jaeger
  name: prod-jaeger-es-query
  namespace: observability
  ownerReferences:
  - apiVersion: jaegertracing.io/v1
    controller: true
    kind: Jaeger
    name: prod-jaeger-es
    uid: 52db4ff1-6acd-4b75-aac8-8d97a0ac4ad6
  annotations:
     # replace all paths with /
    konghq.com/strip-path: 'true'
    konghq.com/protocols: "http,https"
spec: 
  ingressClassName: kong
  rules:
    - http:
        paths:
          - path: /jaeger
            pathType: Prefix
            backend:
              service:
                name: prod-jaeger-es-query
                port:
                  number: 16686

you will see when you hit IP: you will see internal resources not being loaded!

Expected behavior

One shpuld be able to view Jaeger UI correctly

Relevant log output

No response

Screenshot

this is the problem. internal resources dont load

Additional context

No response

Jaeger backend version

v1.52

SDK

Opentelemetry

Pipeline

No response

Stogage backend

No response

Operating system

No response

Deployment model

Kubernetes

Deployment configs

No response