[GitHub] [camel-k] astefanutti commented on issue #1943: operator: option to limit CRs the operator should handle

[GitBox <gi...@apache.org>]

astefanutti commented on issue #1943:
URL: https://github.com/apache/camel-k/issues/1943#issuecomment-822246883


   Right. As we are introducing a mechanism where multiple operators can concurrently manage the same resources, a _locking_ mechanism is necessary. More generally to the rolling upgrade use-case, that mechanism would make sure that only a single operator manages the same resource at a single point in time. That would prevent issues where the label selectors for multiple operators intersect.
   
   Now on how to implement that _locking_ mechanism, I think we could reuse the approach used for locking by multiple replicas of the same operator, that is with a Lease resource, but owned by the Integration. The Lease resource seems the preferred mechanism (by client-go and controller-runtime), and handle use cases such as renewing and deadlining nicely. It would also be another extension of the locking implementation already in place for managing HA of the operator replicas.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org