From 7fe16874f0d39681b41d4d684a58bbc6c2c79f5a Mon Sep 17 00:00:00 2001 From: RaviSantosh Gudimetla Date: Wed, 27 Feb 2019 15:23:03 +0530 Subject: [PATCH] Add cluster-critical priorityClass to machine-api As of now, machine-api-operator doesn't have `system-node-critical` priority, the pods created for this deployment may get evicted by scheduler, if this priorityClass is not available. The rationale behind adding `system-node-critical` is we have nodeSelector to ensure that we are running on master nodes. --- install/0000_30_machine-api-operator_09_deployment.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/install/0000_30_machine-api-operator_09_deployment.yaml b/install/0000_30_machine-api-operator_09_deployment.yaml index 9b5aa5203..e82dbb0bb 100644 --- a/install/0000_30_machine-api-operator_09_deployment.yaml +++ b/install/0000_30_machine-api-operator_09_deployment.yaml @@ -15,6 +15,7 @@ spec: labels: k8s-app: machine-api-operator spec: + priorityClassName: system-node-critical containers: - name: machine-api-operator image: docker.io/openshift/origin-machine-api-operator:v4.0.0