Uploaded image for project: 'Cluster Observability Operator'
  1. Cluster Observability Operator
  2. COO-157

Refactor COO Midstream to use upstream versions

XMLWordPrintable

    • Log Storage - Sprint 253
    • No

      Based on the fact that Cluster-Obervability-Operator v0.3.0 will embrace to use upstream versions for each operand, we have to refactor the midstream configuration to build and publish these versions as below instead of using the product version for every container:

      Component Previous Version Version in v0.3.0 Notes
      Prometheus Operator v0.2.0 v0.71.0  
      Prometheus Config Reloader v0.2.0 v0.71.0  
      Prometheus Admission Webhook v0.2.0 v0.71.0  
      Prometheus v0.2.0 v2.48.1  
      Alertmanager v0.2.0 v0.23.0  
      Thanos v0.2.0 v0.34.1  
      Console Dashboards Plugin v0.2.0 v0.2.0 We align here with the last released version in COO v0.2 to eliminate confusion.
      The plugin itself still declare release-0.1 as the source branch.
      New Components Previous Version Version in v0.3.0 Notes
      Console Logging Plugin - v6.0.0  
      Korrel8r - v0.6.1  

      Developer Notes

      1. Pre-requisite for this change is to get the pipeline/products MR merged and processed: https://gitlab.cee.redhat.com/pipeline/products/-/merge_requests/2569
      2. Post-mortem we need to create a ticket on CLOUDDST project to get the `latest` tag removed for every midstream component above:

              ptsiraki@redhat.com Periklis Tsirakidis
              ptsiraki@redhat.com Periklis Tsirakidis
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: