-
Bug
-
Resolution: Done
-
Normal
-
Logging 5.6.2
-
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:
- Install Loki Operator
- Configure a LokiStack
- Install Red Hat OpenShift Logging operator
- 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
- 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:
- relates to
-
OBSDA-501 Able to set nodeSelector and tolerations for logging-view-plugin pod
- Closed
- links to
- mentioned on
(1 links to, 4 mentioned on)