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
Can we have a way introduced where we can disable the SCC access on the clusterRole and provide all the required SCC before the operator installation?
In some production scenarios, providing SCC access to noobaa-operator cannot be an ideal situation.
Currently the operator fails when we do not have the SCC access in place.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
QUESTION-
Can we have a way introduced where we can disable the SCC access on the clusterRole and provide all the required SCC before the operator installation?
WHY?
In some production scenarios, providing SCC access to noobaa-operator cannot be an ideal situation.
Current Scenario
Currently the operator fails when we do not have the SCC access in place.
The text was updated successfully, but these errors were encountered: