Enhance Node maintanance CRD to include custom labels and taints

[yanirq]

Some maintenance flows will require the addition of custom labels or taints to a node while becoming unschedulable and performing eviction such as fencing, virtual machine migrations and more.

In order to make it possible for the general use the following steps are required:

• Add and optional field to the node maintenance CRD for custom labels.
• Add and optional field to the node maintenance CRD for custom taints.
• When a CR for node maintenance is created holding custom taints/labels - the controller adds them to the node.
• When the CR for node maintenance is deleted (thus removing the node from maintenance) holding custom taints/labels - the controller removes them from the node.
• In case a label/taint already exists - do not add/remove it.

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[yanirq]

/remove-lifecycle stale

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[kubevirt-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[kubevirt-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[kubevirt-bot]

@kubevirt-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

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.