Configure Tolerations, NodeSelector & Resources for collector pods in OpenShift Logging 6

Updated

Starting with Red Hat OpenShift Logging (RHOL) 6, the resources ClusterLogging.logging.openshift.io and ClusterLogForwarder.logging.openshift.io are no longer supported or even available as per the This page is not included, but the link has been rewritten to point to the nearest parent document.OpenShift Logging 6 Release Notes. Due to that, the way the collector is configured is different than how the collector is configured in OpenShift Logging 5.

In OpenShift Logging 6, the configuration for the collector resources (requests and limits), tolerations and nodeSelector are in the clusterlogforwarders.observability.openshift.io.spec.collector CRD.

Collector configuration example


This is just an example, and might need modification as per the `taints` and other configurations in each cluster. 
$ oc edit obsclf -n openshift-logging
[...]
spec:
  collector:
    resources:
      limits:
        memory: 1Gi
      requests:
        cpu: 100m
        memory: 1Gi
    tolerations:
      - effect: NoSchedule
        key: node-role.kubernetes.io/infra
        operator: Exists
      - effect: NoExecute
        key: node-role.kubernetes.io/infra
        operator: Exists
    nodeSelector:   # Use this nodeSelector section only if Collector pods are required only on infra nodes
      node-role.kubernetes.io/infra: ""
  managementState: Managed
[...]
SBR
Product(s)
Category
Components
Tags
Article Type