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

Fix #1943: allow multiple operators to reconcile label filtered resources #2683

Merged
merged 3 commits into from
Oct 12, 2021

Conversation

nicolaferraro
Copy link
Member

Fix #1943

Multiple operators can be configured to only reconcile resources marked with label camel.apache.org/operator.id=<the-operator-id>. This helps e.g. with externally coordinated upgrades.

The operator ID can be set on the operator via the KAMEL_OPERATOR_ID env variable.
By default, normally installed operators (i.e. without ID) don't reconcile resources with a camel.apache.org/operator.id label, so this makes it possible for scoped global operators to share a cluster with a standard global operator.

Release Note

It's possible to assign an ID to a Camel K operator in order to reconcile only a specific set of resources

@nicolaferraro nicolaferraro added the kind/feature New feature or request label Oct 7, 2021
Copy link
Member

@astefanutti astefanutti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great, with this we have multi-tenancy for descoped/global operator!

I'm wondering if there are any reasons that prevent the filtered to be configured at the cache level, like in https://github.com/apache/camel-k/blob/f62e640b2dd422cf5195671ef248dfbadbc92056/pkg/cmd/operator/operator.go. That would prevent the overhead of caching the resources that do not match, as well as sparing the filtering of the associated reconciliation requests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

operator: option to limit CRs the operator should handle
3 participants