template: specify priority class

[maiqueb]

What this PR does / why we need it:
This PR specifies the deployment's priority class, thus assuring the component is not preempted for other workloads with lesses priority.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Release note:

Specify the kubevirt-cluster-critical priorityClass for this deployment. It requires KubeVirt to be deployed.

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from maiqueb. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[oshoval]

what happen if someone tries to deploy it without kubevirt ?
(and the PC doesnt exists)
well he cant anyhow because it listens to VM / VMI i guess so it is non issue

[maiqueb]

what happen if someone tries to deploy it without kubevirt ? (and the PC doesnt exists) well he cant anyhow because it listens to VM / VMI i guess so it is non issue

Yeah, that's kind of the point ... This is a project in the kubevirt org ...

I guess we should add to the docs a note indicating this must be used w/ kubevirt.

Let me check what happens though ...

[oshoval]

Please dont over invest on that, it also happens on KubeSecondaryDNS, and we concluded there it is fine
release note is more than enough imho

[oshoval]

/lgtm

[oshoval]

btw are you sure you want to use this pc ?
i remember that we used the system critical pc and the other one that k8s gives for the components (forgot the name),
we considered components that are mandatory for kubevirt to have higher prio than kubevirt
if it was a DS it was highest prio pc,
if it was a Deployment that could be on any node, it was the one below that, but higher than kubevirt
Petr was in the loop, in case i am wrong