Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-2347

Implement ingress.contextPath for grafana and prometheus

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Won't Do
    • Icon: Minor Minor
    • None
    • None
    • Maistra
    • None
    • 5
    • False
    • Hide

      None

      Show
      None
    • False

      We currently ignore the spec.addons.<addon>.install.service.ingress.contextPath field for grafana and prometheus add-ons. This issue is about implementing it.

      From https://docs.google.com/document/d/13Z7IPQRXVIWGpFzqU9woRT_nr1bE8mcs1Nvq_2rrvkk/edit#heading=h.m8306jv8lurg

      Jaeger doesn't support it, so we'll need validation for that

      Acceptance Criteria:

      • support setting ingress.contextPath on Routes for grafana and prometheus
      • validation should catch it if you're trying to set it on Jaeger - it's not supported
      • operator unit test

              Unassigned Unassigned
              dgrimm@redhat.com Daniel Grimm
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: