Hide Forgot
Description of problem: Specify the nodeSelector in CLO. the nodeSelector is not added into deployment/kibana and cronjob/curator. Version-Release number of selected component (if applicable): v4.x How reproducible: always Steps to Reproduce: 1. Add nodeSelector for ES, kibana,curator as following spec: collection: logs: fluentd: resources: null rsyslog: resources: null type: fluentd curation: curator: nodeSelector: logging: curator resources: null schedule: '*/10 * * * *' type: curator logStore: elasticsearch: nodeCount: 1 nodeSelector: logging: es redundancyPolicy: ZeroRedundancy resources: limits: memory: 2Gi requests: cpu: 200m memory: 2Gi storage: size: 20G storageClassName: gp2 type: elasticsearch 2. Check the nodeSelector in deployment and crontab Actual results: The nodeSelector are added in ES deployment. But it wasn't added to the deployment/kibana and cronjob/curator Expected results: Additional info:
Verified in quay.io/openshift/origin-cluster-logging-operator@sha256:2193bbb23eba530cd76574e0c25f9b3a7f966a7f10f7eb0739f465644614df48
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0758