-
Notifications
You must be signed in to change notification settings - Fork 31
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
[Task] Select default permissions that do not use FlightRecorder/Recording #979
Comments
It's also possible that the downstream build carries a patch for Operator-supplied CRDs. Or maybe the upstream Operator can even carry its own whole |
After reading through the OAuth setup, cryostat/src/main/resources/io/cryostat/net/openshift/OpenShiftAuthManager.properties Line 11 in 74671b8
For cryostat/src/main/resources/io/cryostat/net/openshift/OpenShiftAuthManager.properties Line 12 in 74671b8
For Not sure I worded it right. Any thoughts @ebaron @andrewazores? |
I feel like the |
After #635, we can modify which Cryostat permissions map to which Kubernetes RBAC permissions. Now we should modify the default Kubernetes permissions from their current values. Since the FlightRecorder and Recordings APIs will soon be removed, we have to pick some alternatives. Ideally these would not depend on CRDs shipped with the operator, but that's not a hard requirement, it would simply allow for more flexibility.
The text was updated successfully, but these errors were encountered: