Skip to content

Revisit capabilities scope (namespace vs cluster) #233

Open
@jesusmah

Description

@jesusmah

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.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions