Bug 1733314 - toleration field in clusterlogging resource not honored
Summary: toleration field in clusterlogging resource not honored
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.1.z
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Jeff Cantrill
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-25 16:29 UTC by raffaele spazzoli
Modified: 2019-07-25 18:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-25 18:25:14 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description raffaele spazzoli 2019-07-25 16:29:32 UTC
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.

Comment 1 Jeff Cantrill 2019-07-25 18:25:14 UTC
Tolerations arent supported until 4.2: https://jira.coreos.com/browse/LOG-392


Note You need to log in before you can comment on or make changes to this bug.