Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-6103

Allow CLO 5.8 on OCP 4.16 and 4.17 until 5.8 EOL

XMLWordPrintable

    • False
    • None
    • False
    • NEW
    • NEW
    • Hide
      Before this update, the Red Hat OpenShift Logging Operator was missing on 4.16 and forward catalogs caused Telco customers not being able to finish their certifications on upcoming 6.0 on time. With this update, the Red Hat OpenShift Logging Operator is available on 4.16 and 4.17 resolves the issue.
      Show
      Before this update, the Red Hat OpenShift Logging Operator was missing on 4.16 and forward catalogs caused Telco customers not being able to finish their certifications on upcoming 6.0 on time. With this update, the Red Hat OpenShift Logging Operator is available on 4.16 and 4.17 resolves the issue.
    • Bug Fix
    • Log Collection - Sprint 259, Log Collection - Sprint 260

      Description of problem:

      Telco customer has expressed challenges associated with the fact that Logging 5.8 is absent from OCP 4.16 and 4.17 clusters.  These customer's are preparing to certify on OCP 4.16 and 4.17 but do not have the capacity to include Logging 6.0 which GA has been delayed.  They require Logging 5.8 on OCP 4.16 and 4.17.

      Version-Release number of selected component (if applicable):

      How reproducible:

      Steps to Reproduce:

      1.  
      2.  
      3. ...

      Actual results:

      Expected results:

      Based upon discussion with Telco team and Logging PM:

      • Make Logging 5.8 available on OCP 4.16 and 4.17
      • Add statement to CSV page visible in OLM regarding the hard stop in support on 4.17 for Oct. 2025.

       

      Additional info:

            ptsiraki@redhat.com Periklis Tsirakidis
            jcantril@redhat.com Jeffrey Cantrill
            Anping Li Anping Li
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: