ingress for jaeger not respected by operator

[volleynator]

Description When defining ingress with jaeger.spec.query.ingress, the operator does not respect the set values, instead, it deploys an almost empty ingress.

Versions helm: version.BuildInfo{Version:"v3.5.3", GitCommit:"041ce5a2c17a58be0fcd5f5e16fb3e7e95fea622", GitTreeState:"dirty", GoVersion:"go1.15.8"} chart: jaeger-operator-2.21.0

values.yaml

jaeger:
  spec:
    query:
      ingress:
        enabled: false
        annotations:
          traefik.ingress.kubernetes.io/router.tls: "true"
          traefik.ingress.kubernetes.io/rewrite-target: /
        tls:
          - hosts:
              - example.com
        hosts:
          - host: example.com
            paths:
              - path: /jaeger
                backend:
                  serviceName: jaeger-operator-jaeger-query
                  servicePort: 80

actual ingress created

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  creationTimestamp: "2021-05-18T15:24:31Z"
  generation: 1
  labels:
    app: jaeger
    app.kubernetes.io/component: query-ingress
    app.kubernetes.io/instance: jaeger-test-jaeger-operator-jaeger
    app.kubernetes.io/managed-by: jaeger-operator
    app.kubernetes.io/name: jaeger-test-jaeger-operator-jaeger-query
    app.kubernetes.io/part-of: jaeger
  managedFields:
  - apiVersion: networking.k8s.io/v1beta1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:labels:
          .: {}
          f:app: {}
          f:app.kubernetes.io/component: {}
          f:app.kubernetes.io/instance: {}
          f:app.kubernetes.io/managed-by: {}
          f:app.kubernetes.io/name: {}
          f:app.kubernetes.io/part-of: {}
        f:ownerReferences:
          .: {}
          k:{"uid":"7986a7b0-8c4b-40cd-85ba-aa16b1973e0e"}:
            .: {}
            f:apiVersion: {}
            f:controller: {}
            f:kind: {}
            f:name: {}
            f:uid: {}
      f:spec:
        f:backend:
          .: {}
          f:serviceName: {}
          f:servicePort: {}
    manager: jaeger-operator
    operation: Update
    time: "2021-05-18T15:24:31Z"
  name: jaeger-test-jaeger-operator-jaeger-query
  namespace: jaeger
  ownerReferences:
  - apiVersion: jaegertracing.io/v1
    controller: true
    kind: Jaeger
    name: jaeger-test-jaeger-operator-jaeger
    uid: 7986a7b0-8c4b-40cd-85ba-aa16b1973e0e
  resourceVersion: "3685168"
  uid: 53eaf66e-b0f9-486e-adee-df602969f67d
spec:
  defaultBackend:
    service:
      name: jaeger-test-jaeger-operator-jaeger-query
      port:
        number: 16686
status:
  loadBalancer: {}

Expected behaivour The Operator creates an ingress as defined in jaeger.spec.query.ingress

[rafaribe]

I also experienced some strange behavior with the Ingress, In my case I wanted to disable it. However, I could only do it by setting the jaeger.spec.ingress.enabled value to false. Maybe give it a shot to include your configuration in that key.

[shree007]

I am facing same issue. UI is appearing as empty.

[gugugubo]

I got into the same dilemma and spent a night trying to solve it