[DOWNSTREAM-ONLY] add ocs default toleration to controller podspec

[leelavg]

all components deployed as part of odf should tolerate this taint by default "node.ocs.openshift.io/storage=true:NoSchedule"

part of https://bugzilla.redhat.com/show_bug.cgi?id=2315651

[Rakshith-R]

@leelavg have we considered doing it through tolerations on subscription ?
https://github.com/operator-framework/operator-lifecycle-manager/blob/master/doc/design/subscription-config.md#tolerations

Refer to https://github.com/red-hat-storage/kubernetes-csi-addons/tree/main/redhat for adding downstream only change

[leelavg]

have we considered doing

• yes, but not possible as mentioned in the linked PR controllers: add ocs default toleration to csi driver spec ocs-client-operator#251 (comment)

adding downstream only change

• if I do that now, I'm landing on this PR itself.

[Rakshith-R]

have we considered doing

• yes, but not possible as mentioned in the linked PR controllers: add ocs default toleration to csi driver spec ocs-client-operator#251 (comment)

okay thanks.

adding downstream only change

• if I do that now, I'm landing on this PR itself.

https://github.com/red-hat-storage/kubernetes-csi-addons/blob/main/.github/PULL_REQUEST_TEMPLATE/redhat-downstream-only.md

I meant structure the commit and pr title/description accordingly similar to #30 so its easy distinguish from regular commits

[leelavg]

its easy distinguish from regular commits

• ack, done. Let me know if there are any mistakes. thanks!

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: leelavg, Rakshith-R

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 [Rakshith-R]

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

[leelavg]

/cherrypick release-4.17

[openshift-cherrypick-robot]

@leelavg: once the present PR merges, I will cherry-pick it on top of release-4.17 in a new PR and assign it to you.

In response to this:

/cherrypick release-4.17

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-sigs/prow repository.

[openshift-cherrypick-robot]

@leelavg: new pull request created: #212

In response to this:

/cherrypick release-4.17

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-sigs/prow repository.