-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enforce Installation of the Operator on stateless Nodepools #2707
Comments
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. |
Hi @GeekYiwen , |
Hi @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 |
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
andtolerations
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
The text was updated successfully, but these errors were encountered: