Loki doesn't watch the `spec.storage.tls.caName` for updating the status in RHOCP 4

Solution Verified - Updated -

Issue

  • The Loki Operator is not reviewing the status of the spec.storage.tls.caName configmap
  • When it was created the LokiStack custom resource (CR), it was defined the name of the configmap containing the CA in spec.storage.tls.caName, but, the configmap didn't exist and although it was created later, the LokiStack was not taking it into consideration and deploying the Loki pods using the CA
  • It was updated the CA contained in the configmap defined in the LokiStack CR in spec.storage.tls.caName, but the Loki pods were not restarted automatically mounting the new CA

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    *
  • Red Hat OpenShift Logging (RHOL)
    • 5.6
    • 5.7
    • 5.8
    • 5.9
  • Loki Operator
  • LokiStack
  • Network Observability

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content