(feat) Selectively onboard CAPI clusters #450
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Deploying Sveltos on a management cluster with hundreds of existing CAPI clusters results in all clusters being onboarded immediately. This can lead to a rapid creation of hundreds of sveltos-agent deployments in the management cluster, potentially causing performance issues. Therefore, a gradual onboarding mechanism is preferable.
This pull request introduces such a mechanism. By using an annotation, Sveltos can selectively identify which CAPI clusters to manage. When this annotation is specified, Sveltos will only onboard those CAPI clusters that have it.
This feature allows for gradual onboarding, which is particularly beneficial in management clusters with a large number of pre-existing CAPI clusters.