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

Loki Operator - Add support for seamless upgrades to use TSDBv3 and Schema V13

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • Logging 5.9.0
    • Logging 5.9.0
    • Log Storage
    • None
    • Log Storage - Sprint 243, Log Storage - Sprint 244, Log Storage - Sprint 245, Log Storage - Sprint 246, Log Storage - Sprint 247

      Description

      As a LokiStack administrator I want to be able to define a additional ObjectStorageSchema using V13 and TSDBv3 for an effective date in the future, so that newer incoming logs are eligible to use the structured metadata indexing capabilities.

      Acceptance Criteria

      1. The LokiStack administrator can define an additional schema without breaking access to stored logs in previous schemas (V11/V12) and indexed by boltdb-shipper.
      2. The LokiStack administrator can see in the resource status or per alert if the old logs (using V11/V12 and boltdb-shipper) fall out of retention and is able to drop the old schema.

      Developer Notes

      1. Boltdb-shipper to TSDB Migration Docs
      2. Considering if the above migration docs imply additions/validation for the LokiStack limits config.
      3. Evaluate if an alert or resource status condition can be use to nudge people to upgrade from the present default schema (V11) to V13.
      4.  

              btaani@redhat.com Bayan Taani
              ptsiraki@redhat.com Periklis Tsirakidis
              Kabir Bharti Kabir Bharti
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: