Description
Feature Description
It should be possible to run multiple agents powering the same API, as long as those agents only work on distinct objects (for example based on a label selector (which is not yet possible in the agent)).
If and when this becomes possible, multiple agents would fight over who owns the APIResourceSchemas and the APIExport, leading to reconcile loops across all of the agents. There needs to be a way to ensure only a single agent is actively managing the APIExport/ARS.
Proposed Solution
I would not suggest classic leader election, as it could happen that the leader lease is lost and then another agent pick it up, but the other agent is on another cluster with slightly different CRDs, leading to confusion. I think the "CRD manager"-agent should be determined by a human on a single cluster, maybe via a flag in the Helm chart?
Alternative Solutions
No response
Want to contribute?
- I would like to work on this issue.
Additional Context
No response