Description of problem:
the clusterlogging CRD has a toleation field for the elasticsearch portion. When I set a value on this field, the corresponding deployment to not receive it.

cluster logging toleration fragment:

  logStore:
    elasticsearch:
      nodeCount: 3
      nodeSelector:
        node-role.kubernetes.io/es: ''
      redundancyPolicy: SingleRedundancy
      resources:
        limits:
          cpu: '1'
          memory: 8Gi
        requests:
          cpu: '1'
          memory: 8Gi
      storage:
        size: 200G
        storageClassName: gp2
      tolerations:
        - effect: NoSchedule
          key: node-role.kubernetes.io/es
          operator: Exists

elasticsearch CR fragment:

  nodeSpec:
    image: >-
      registry.redhat.io/openshift4/ose-logging-elasticsearch5:v4.1.4-201906271212
    nodeSelector:
      node-role.kubernetes.io/es: ''
    resources:
      limits:
        cpu: '1'
        memory: 8Gi
      requests:
        cpu: '1'
        memory: 8Gi
  nodes:
    - genUUID: yuw10mxq
      nodeCount: 3
      resources: {}
      roles:
        - client
        - data
        - master
      storage:
        size: 200G
        storageClassName: gp2
  redundancyPolicy: SingleRedundancy

deployment fragment:

      dnsPolicy: ClusterFirst
      tolerations:
        - key: node.kubernetes.io/disk-pressure
          operator: Exists
          effect: NoSchedule


notice that in the elasticsearch CR there are no tolerations defined and that in the deployment there is one toleration, but it's not the one we need.