Requirement
In recent releases we have deprecated the "multiple operators" feature [1]. The main reason is that the model provided was opening security constraints, where any user can escalate privileges by picking an operator for which they may have not enough privileges.
Right now we officially supports:
- Global (descoped) operator: an operator that reconciles all resources at cluster level
- Namespaced operator: an operator that reconciles only resources in a given namespace
We miss the possibility to run a "Multi namespace operator", which is a way to let the user provide a sharding model when the number of namespaces scales. The goal is that with this model, it is the operator that has to pick up a selected (configurable by operator admin) number of namespaces.
The only potential challlenge is the need to provide namespaced RBAC for each namespace.
[1] https://camel.apache.org/camel-k/next/installation/advanced/multi.html
Requirement
In recent releases we have deprecated the "multiple operators" feature [1]. The main reason is that the model provided was opening security constraints, where any user can escalate privileges by picking an operator for which they may have not enough privileges.
Right now we officially supports:
We miss the possibility to run a "Multi namespace operator", which is a way to let the user provide a sharding model when the number of namespaces scales. The goal is that with this model, it is the operator that has to pick up a selected (configurable by operator admin) number of namespaces.
The only potential challlenge is the need to provide namespaced RBAC for each namespace.
[1] https://camel.apache.org/camel-k/next/installation/advanced/multi.html