-
Story
-
Resolution: Done
-
Major
-
0.14.0
-
None
Currently, our deployment of kogito-operator is namespace-scoped, i.e: we need to deploy our operator in every namespace in which we would want to run kogito services.
For more flexibility, we should give more options like installing operator in a cluster-scoped or multi-namespace scoped fashion. In cluster-scoped a single operator deployment in its own namespace will manage all kogito services in all namespaces. In multi-namespace, we can take a list of namespaces input from users and make our operator watch only those namespaces for the kogito services.
- blocks
-
KOGITO-3067 Migrate to Operator SDK 1.x
- Resolved
- incorporates
-
KOGITO-2561 Install Kogito operator using OLM on Kubernetes environment
- Closed
- is blocked by
-
KOGITO-3225 SA deployments for cluster/multi-scoped operator
- Closed
- is related to
-
KOGITO-3938 BDD tests: Add option to run tests with Kogito cluster wide operator
- Resolved