IBM Support

Pre-emptive Upgrade of Red Hat OpenShift Logging Operator from 5.9 to 6.2 due to Elasticsearch End of Support

Question & Answer


Question

  • Why is a pre-emptive upgrade of the OpenShift Logging Operator required when Elasticsearch reaches end of support?
  • What platform-level changes occur when upgrading OpenShift Logging from version 5.9 to 6.2?
  • How does the removal of in-cluster Elasticsearch affect OpenShift logging architecture?
  • What are the supported log storage and forwarding options after upgrading to Logging Operator 6.x?
  • How should ClusterLogForwarder be configured to forward logs to external systems such as Kafka or Logstash?
  • What common causes can lead to partial or missing log forwarding after upgrading the Logging Operator?
  • What validation steps should be performed before and after upgrading the OpenShift Logging Operator to ensure log pipeline integrity?

Answer

Refer RH Documentation: https://access.redhat.com/articles/7089860 

 

[{"Type":"MASTER","Line of Business":{"code":"LOB33","label":"N\/A"},"Business Unit":{"code":"BU051","label":"N\/A"},"Product":{"code":"SSR5HY","label":"Cloud Pak RHOCP COC"},"ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":""}]

Document Information

Modified date:
20 March 2026

UID

ibm17267013

Page Feedback