Add CriticalAddonsOnly toleration for rook-ceph-operator
rook-ceph-operator is being deployed during initinfra-target and needs to be scheduled on tainted node-role.kubernetes.io/master node. Change-Id: I648a60f06cd615085ffd19bb6c1b5cebb974ef0f Signed-off-by: Andrii Ostapenko <andrii.ostapenko@att.com>
This commit is contained in:
parent
6dc74ed576
commit
d485dcc9c8
|
@ -1,2 +1,4 @@
|
|||
resources:
|
||||
- upstream
|
||||
patchesStrategicMerge:
|
||||
- rook-operator-patch-tolerations.yaml
|
||||
|
|
|
@ -0,0 +1,14 @@
|
|||
apiVersion: apps/v1
|
||||
kind: Deployment
|
||||
metadata:
|
||||
name: rook-ceph-operator
|
||||
namespace: rook-ceph # namespace:operator
|
||||
spec:
|
||||
template:
|
||||
spec:
|
||||
tolerations:
|
||||
# Mark the pod as a critical add-on for rescheduling.
|
||||
- key: CriticalAddonsOnly
|
||||
operator: Exists
|
||||
- key: node-role.kubernetes.io/master
|
||||
effect: NoSchedule
|
Loading…
Reference in New Issue