[Helm] Dont force deployment on control nodes

[adrianchiris]

use preferred scheduling instead.

This is desired for a better user experience
on managed k8s clusters where control plane nodes
are not part of the cluster

[github-actions]

Thanks for your PR,
To run vendors CIs use one of:

• /test-all: To run all tests for all vendors.
• /test-e2e-all: To run all E2E tests for all vendors.
• /test-e2e-nvidia-all: To run all E2E tests for NVIDIA vendor.

To skip the vendors CIs use one of:

• /skip-all: To skip all tests for all vendors.
• /skip-e2e-all: To skip all E2E tests for all vendors.
• /skip-e2e-nvidia-all: To skip all E2E tests for NVIDIA vendor.
  Best regards.

[coveralls]

Pull Request Test Coverage Report for Build 5055011305

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 2 unchanged lines in 1 file lost coverage.
• Overall coverage increased (+0.04%) to 25.606%

---

Files with Coverage Reduction	New Missed Lines	%
controllers/sriovibnetwork_controller.go	2	66.04%

Totals
Change from base Build 5022019978:	0.04%
Covered Lines:	1934
Relevant Lines:	7553

---

💛 - Coveralls

[adrianchiris]

@e0ne @Eoghan1232 PTAL, this one is straight forward

[Eoghan1232]

lgtm.

question: do you want them to have the same weight value assigned? this would mean the scheduler would check both at the same time, and choose whichever one is best to deploy on.
should one be a higher priority?

[adrianchiris]

question: do you want them to have the same weight value assigned? this would mean the scheduler would check both at the same time, and choose whichever one is best to deploy on.
should one be a higher priority?

in this case its fine to have both with same weight. generally in a cluster you would either have one set for control plane nodes or both.

latest deployments with kubeadm just set the control-plane label.
i kept the "master" label for backward compat.