-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
None
-
False
-
Release Notes
-
Bug Fix
-
In Progress
-
-
-
Sprint 62
If you add the following snippet to the SMCP, the nodeSelector is passed to the Jaeger resource, but the tolerations are not.
spec:
runtime:
defaults:
pod:
nodeSelector:
node-role.kubernetes.io/infra: ""
tolerations:
- effect: NoSchedule
key: node-role.kubernetes.io/infra
value: reserved
- effect: NoExecute
key: node-role.kubernetes.io/infra
value: reserved
This results in the Jaeger pod being stuck in Pending state:
$ oc describe pod jaeger-xyz Warning FailedScheduling 42s default-scheduler 0/6 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/infra: reserved}, 3 node(s) had untolerated taint {node-role.kubernetes.io/master: }, 5 node(s) didn't match Pod's node affinity/selector. preemption: 0/6 nodes are available: 6 Preemption is not helpful for scheduling.
