Enforce Installation of the Operator on stateless Nodepools

[GeekYiwen]

Is your feature request related to a problem? Please describe.
As Kanister is a stateless operator I would like to enforce that Kanister will be running on a stateless nodepool. Many other K8s operators allow the option to specify nodeSelector and tolerations in the values file to enforce this.

Describe the solution you'd like
Add the possibility to enforce the installation of the Kanister operator on a stateless nodepool. This should be done by passing values in the helm chart.

Example Values

nodeSelector:
  node_pool: "stateless"

tolerations:
  - key: "dedicated"
    operator: "Equal"
    value: "stateless"
    effect: "NoSchedule"

[github-actions]

Thanks for opening this issue 👍. The team will review it shortly.

If this is a bug report, make sure to include clear instructions how on to reproduce the problem with minimal reproducible examples, where possible. If this is a security report, please review our security policy as outlined in SECURITY.md.

If you haven't already, please take a moment to review our project's Code of Conduct document.

[viveksinghggits]

Hi @GeekYiwen ,
Thank you for reporting this. We discussed about this in the last community call and we think that it would be a great addition to the project. We will work on this soon.
If you have some bandwidth and want to work on this, let us know and we would be more than happy to help.

[GeekYiwen]

Hi @viveksinghggits,
Thanks for tackeling this issue :D Sadly I am not that experienced in writing Golang and therefore don't think, that I can contribute any meaningful code for this issue. If there is any insights into the issue that you need I am happy to answer any questions if I know more about this. Thanks in advance for implementing 👍

[viveksinghggits]

Sounds good @GeekYiwen . No problem, we will take this up. And for now we will make sure that users are able to configure the nodeSelector and tolerations fields of kanister-operator pod as part of this issue.