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

Unability to configure nodePlacement and toleration for logging-view-plugin

XMLWordPrintable

    • False
    • None
    • False
    • NEW
    • ON_QA
    • Before this update, the logging view plugin did not allow for custom node placement and tolerations. This update adds the ability to define node placement and tolerations for the logging view plugin.
    • Bug Fix
    • Log Collection - Sprint 235, Log Collection - Sprint 236, Log Collection - Sprint 237

      Description of problem: 
      Previously with Kibana we were capable to configure nodePlacement for this pod. Now we are replacing Kibana by console plugin we don't have this possibility for logging-view-plugin

      Version-Release number of selected component (if applicable): 5.6.2

      How reproducible:

      Steps to Reproduce:

      1. Install Loki Operator
      2. Configure a LokiStack 
      3. Install Red Hat OpenShift Logging operator
      4. Configure ClusterLogging:
      apiVersion: logging.openshift.io/v1
      kind: ClusterLogging
      metadata:
        name: instance
        namespace: openshift-logging
      spec:
        collection:
          type: vector
        logStore:
          lokistack:
            name: logging-loki
          type: lokistack
        managementState: Managed 
      1. There is no possibility to configure nodePlacement and tolerations for logging-view-plugin.

      Actual results: 
      logging-view-plugin is scheduled on any worker nodes{}

      Expected results:

      logging-view-plugin is scheduled on nodes having nodeSelector and taints configured in ClusterLogging

      Additional info:

            rh-ee-calee Calvin Lee
            laurent.tourreau Laurent TOURREAU
            Giriyamma Karagere Ramaswamy Giriyamma Karagere Ramaswamy (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: