Control plane, Assign Priority class to pods

[oshoval]

Add system-node-critical to nmstate-handler,
since this pod should run on each node,

Add system-cluster-critical to nmstate-webhook
and to nmstate-cert-manager pods,
since those pods aren't bound to a specific node,
yet those are important control plane pods.

This will make the control plane less sensitive to preemption
than user workloads.

Signed-off-by: Or Shoval [email protected]

None

[kubevirt-bot]

Hi @oshoval. Thanks for your PR.

I'm waiting for a nmstate member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[oshoval]

@qinqon need ok to test please and review if possible

[phoracek]

/ok-to-test

[oshoval]

I don't think the failure is due to this PR

/retest

[qinqon]

/lgtm
/approve

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qinqon

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [qinqon]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[oshoval]

/cherry-pick release-0.47

[kubevirt-bot]

@oshoval: only nmstate org members may request cherry picks. You can still do the cherry-pick manually.

In response to this:

/cherry-pick release-0.47

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.