Description of problem: To schedule build pods in dedicated nodes, the buildOverride parameter in the master-config.yaml is appended with tolerations and a node is tainted with respective kay value pair. After initializing the build the pod seems to schedule on random node even it is appended with toleration values. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Edit the master-config.yaml and in the buildoverrides section define the necessary tolerations. Restart the master api and controllers. 2. Taint a node with matching key-value pair. 3. Try launching a new application and observe on which node the build pod is running Actual results: The `build pod` gets scheduled on random node irrespective of the configuration Expected results: The `build pod` should be scheduled on a tainted node matching the toleration of the pod. Additional info: The same configuration is working fine if `nodeSelector` variable is used instead of `taint-toleration`.
Can you add the master-config.yaml you are using?
Any progress on the issue?
**Updated docs PR number** https://github.com/openshift/openshift-docs/pull/22242
Thanks Michael.
The updates look good to me
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-2020:2477