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

Override 'schedulerName' for each Loki component in the LokiStack custom resource

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • Logging 5.8, Logging 5.9
    • PM Logging
    • None
    • False
    • None
    • False
    • Not Selected
    • 0
    • 0
    • 0% 0%
    • 0

      Proposed title of this feature request

      Override 'schedulerName' for each Loki component in the LokiStack custom resource

      Description: 

      Users of Portworx storage are requesting the implementation of a storage-conscious scheduler configuration. While performance is important, users prioritize storage considerations as well. Portworx operates by utilizing locally attached storage on each node. However, issues arise when the default scheduler places pods on nodes without the necessary replicas, leading to pod errors. Although a workaround utilizing a Portworx 'shared' storage class with NFS exists, users are seeking a more effective solution through an enhanced storage-conscious scheduler.

      REF: https://docs.portworx.com/portworx-enterprise/operations/operate-kubernetes/storage-operations/stork 
       

            jamparke@redhat.com Jamie Parker
            nikijain@redhat.com Nikita Jain
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: