Skip to content

(feat) Selectively onboard CAPI clusters #450

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

Merged
merged 1 commit into from
Feb 23, 2025

Conversation

gianlucam76
Copy link
Member

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.

@gianlucam76 gianlucam76 force-pushed the onboard-capi-cluster branch 2 times, most recently from a9cccd7 to 5b5b6ac Compare February 22, 2025 14:55
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.
@gianlucam76 gianlucam76 merged commit 059245f into projectsveltos:main Feb 23, 2025
2 checks passed
@gianlucam76 gianlucam76 deleted the onboard-capi-cluster branch February 23, 2025 06:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant