Uploaded image for project: 'Observability and Data Analysis Program'
  1. Observability and Data Analysis Program
  2. OBSDA-1076

Loki Operator able to manage the rollout of the Loki pods when the storageClass changes

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • Logging 6.0, Logging 6.1
    • Log Storage, PM Logging
    • None
    • False
    • None
    • False
    • Not Selected
    • 0

      Proposed title of this feature request

      Loki Operator able to manage the rollout of the Loki pods when the storageClass changes

      What is the nature and description of the request?

      Loki CR allows to change the storageClass, but it's not doing automatically the rollout of the Loki pods recreating the PVC/PV to use the new storageClass.

      It should be expected that the Loki Operator could manage this "rollout" with the new SC set and managing to scale up/down flushing the WAL similar as it's described in the upstream documentation "How to scale up/down" [0][1]

      Why does the customer need this? (List the business requirements)

      This type of tasks are those that it should be expected to be managed by an Operator making easy the life to the OpenShift admins and simplifying the tasks and less prone to errors

      List any affected packages or components.

      Loki Operator

       [0] https://grafana.com/docs/loki/latest/operations/storage/wal/#how-to-scale-updown
       [1] https://grafana.com/docs/loki/latest/operations/storage/wal/#additional-notes

              jamparke@redhat.com Jamie Parker
              rhn-support-ocasalsa Oscar Casal Sanchez
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: