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

Revisit capabilities scope (namespace vs cluster) #233

Open
jesusmah opened this issue Mar 21, 2022 · 0 comments
Open

Revisit capabilities scope (namespace vs cluster) #233

jesusmah opened this issue Mar 21, 2022 · 0 comments
Assignees

Comments

@jesusmah
Copy link
Contributor

Creating this issue to revisit the different capabilities the Cloud Pak Production Deployment Guides allow a user to install for collisions on their scopes. That is, we often encounter people with issues because they install a capability cluster-wide while another is namespace-wide making certain operators to get installed in multiple namespaces and failing as a result.

This usually gets fixed by installing all capabilities cluster-wide but there might be some capabilities that must be installed namespace wide such as Process Mining.

Let's review the scopes of these and come up with a strategy that works for all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants