-
Notifications
You must be signed in to change notification settings - Fork 344
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
Allow multiple operators in a single namespace #3397
Comments
This issue has been automatically marked as stale due to 90 days of inactivity. |
I think there is the opportunity to expand a little bit the scope of this issue by also provide a way to have multiple versions of the camel-k operator installed in parallel using label selection to restrict the resources each camel-k operator should watch and reconcile. This would also hopefully simplify requiring a specific installation of the camel-k operator using the camel-k bundle without requiring to hand craft and tweak deployments. Current StateThe camel-k bundle sets up a camel-k operator upon installation which then relies on IntegrationPlatforms to configure its behavior. The IntegrationPlatform is meant to:
Even if some initial support for having multiple running camel-k operators exists, in order to have another operator installed, a deployment must be hand crafted and deployed to kubernetes resulting in additional manual work to be done and increasing the complexity of handling updated as the deployment must be amended manually as the camel-k bundle is not aware of such additional operators. Also, dealing with multiple IntegrationPlatforms is very confusing, it is not used very often and discouraged. Proposed stateIntroduce a new model where the IntegrationPlatform is not used only to configure some aspect of the operator, but also as a way to request the deployment of a specific Camel K operator. Within this model there won’t be a single camel-k operator dealing with a multitude of configurations and behaviors but a number of camel-k operators reconciling specific resources potentially with specific requirements and behaviors. To make this possible the camel-k operator needs to be split (at least from a responsibility point of view) into:
|
How do you view the CRD upgrade changes and the different controller versions ? |
This is a follow-up on #3358
We should allow to install multiple operators in a single namespace for the sake of multi operator handling on a single cluster. At the moment we have static operator resource names (e.g. deployment name is
camel-k-operator
) so there can only be one single operator per namespace.When dealing with multi tenancy on a cluster we should be able to run multiple (global) operators in a single namespace.
The text was updated successfully, but these errors were encountered: