-
Notifications
You must be signed in to change notification settings - Fork 12
Closed
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.
Description
Feature Description
I have multiple kcp setups, and I now want to connect them all to the same service provider. At the moment the syncagent was written under the asumption that only 1 syncagent handles exactly 1 APIExport/APIGroup.
But I have many kcp's, all offering the same API, that I need to connect to a single service cluster.
Proposed Solution
I could see multiple solutions:
- A sync-agent could label the resources it has created with its own name. This would allow them to only watch those that they own. This is simple to achieve, but would still require 1 syncagent per kcp.
- The sync-agent natively supports connecting to many kcps. This would require significant code changes and opens the question how the sync agent would discover new kcp's. Also caching might be a problem, plus it could cause a single-point-of-failure when the sync-agent dies.
Alternative Solutions
No response
Want to contribute?
- I would like to work on this issue.
Additional Context
No response
Metadata
Metadata
Assignees
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.