feat: parametrization of deployment strategy for csi controller

[mariouhrin]

What type of PR is this?
/kind feature

What this PR does / why we need it:
It allows the options to override default deployment strategy for csi controller (from RollingUpdate to Recreate).

In my company, we are using single node k3s cluster. We had an issue with already allocated port after new deployments of csi-driver-nfs helm chart.

This is the error logs from csi controller pod:
Warning  FailedScheduling  12m (x42 over 44m)   default-scheduler  0/1 nodes are available: 1 node(s) didn't have free ports for the requested pod ports.

The problematic port was this one (csi controller deployment manifest):

- containerPort: 29652                                                                                                                                                                                                                              
  hostPort: 29652                                                                                                                                                                                                                                            
  name: healthz                                                                                                                                                                                                                                     
  protocol: TCP

The Recreate deployment strategy helped us to avoid this already allocated port issue. The RollingUpdate deployment strategy is probably causing a problem when the old and new pods are running at the same time and 29652 port cannot be used for new pod. But maybe I am wrong.

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

feat: parametrization of deployment strategy for csi controller

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: mariouhrin (9a3af58)

[k8s-ci-robot]

Hi @mariouhrin. Thanks for your PR.

I'm waiting for a kubernetes-csi 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.

[coveralls]

Pull Request Test Coverage Report for Build 3060582475

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 77.411%

---

Totals
Change from base Build 2950440187:	0.0%
Covered Lines:	610
Relevant Lines:	788

---

💛 - Coveralls

[andyzhangx]

/ok-to-test

[andyzhangx]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andyzhangx, mariouhrin

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 [andyzhangx]

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