Skip to content
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

Support AllNamespaces install mode #502

Closed
Tracked by #501
ebaron opened this issue Dec 1, 2022 · 1 comment · Fixed by #514
Closed
Tracked by #501

Support AllNamespaces install mode #502

ebaron opened this issue Dec 1, 2022 · 1 comment · Fixed by #514
Assignees
Labels
feat New feature or request needs-documentation

Comments

@ebaron
Copy link
Member

ebaron commented Dec 1, 2022

We want to move to a model where the operator can manage multiple Cryostat installations in across different namespaces. In order to do this, we should support the AllNamespaces install mode, where the operator watches its CRs in all namespaces.

In addition, this will help prepare us for the next generation of OLM APIs: operator-framework/operator-lifecycle-manager#2437.

@ebaron ebaron added the feat New feature or request label Dec 1, 2022
@andrewazores andrewazores moved this to Todo in 2.3.0 release Dec 6, 2022
@andrewazores
Copy link
Member

See https://github.com/cryostatio/cryostat/pull/1290 . The Cryostat server now supports querying for discovery across namespaces if the right environment variable is set. This doesn't add any enhanced permissions model to ensure that users should have access to targets or archived recording files, so it would still rely on the Operator to create instances with the right Roles/Rolebindings as specified by the user's configuration (via multiple Cryostat CRs). It's then on the user to create configurations that make sense so that the Cryostat CRs correspond to meaningfully grouped users with similar roles and permissions levels.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat New feature or request needs-documentation
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants