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

Use vanilla prometheus instead of our fork

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • OSSM 2.4.0
    • None
    • Maistra
    • None
    • Sprint 56, Sprint 57, Sprint 58 - week 1, Sprint 58 - week 2 and 3, Sprint 59, Sprint 60, Sprint 61, Sprint 62

      We have in the past forked prometheus and added code to read SMMR's configuredMembers and use MultiNamespaceListWatchers to only watch those namespaces. This shouldn't be necessary, as prometheus can be configured to only scrape a defined set of namespaces. If we can use that, we can get rid of the fork and deploy standard prometheus images - or at least build our prometheus image from existing RHEL RPMs - which will radically simplify our build/release processes.

      Acceptance Criteria:

      • we're no longer building prometheus from source
      • namespaces to be scraped are configured by the operator

              rh-ee-yannliu Yann Liu
              dgrimm@redhat.com Daniel Grimm
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: