We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When I try to install litmus 2.0.32 using a namespace-scoped account, the installation fails.
This is because the role we use asks for nodes and namespaces permissions, which is not namespace scoped.
nodes
namespaces
The text was updated successfully, but these errors were encountered:
What is the downside of not having those permissions? Could they be made optional in the helm chart?
Sorry, something went wrong.
Yes, these are some extra permission. I will raise a PR to remove it. Thanks for pointing this.
Meanwhile, you can use this k8s manifest in namespace mode- https://github.com/litmuschaos/litmus/blob/master/mkdocs/docs/2.0.0/litmus-namespaced-2.0.0.yaml
Hi @rberrelleza , We have already removed the higher permission in namespace scoped service account. Thanks for opening it.
No branches or pull requests
When I try to install litmus 2.0.32 using a namespace-scoped account, the installation fails.
This is because the role we use asks for
nodes
andnamespaces
permissions, which is not namespace scoped.The text was updated successfully, but these errors were encountered: