Repository navigation
feat: Let one sveltos-agent serve several clusters - #535
Merged
Merged
Conversation
Add --agent-clusters-per-instance. When greater than one, classifier deploys in the management cluster a single sveltos-agent Deployment for up to N clusters, instead of one Deployment per cluster. The clusters sharing a Deployment (a group) are recorded in a ConfigMap with the same name as the Deployment, using libsveltos agentgroup. The flag applies only to agentless mode. It is ignored when the agent runs in the managed cluster, in pull mode, and when N is 1. The group Deployment is removed when its last member leaves, and members whose cluster is gone are removed by a periodic sweep. Only global agent patches apply to a group. The agentless sveltos-agent Role gains access to configmaps. Add unit tests and a post-merge FV job, FV_AGENTLESS_GROUPING, running make create-cluster-agentless-grouping fv-agentless-grouping.
gianlucam76
force-pushed
the
agent-grouping
branch
from
November 7, 2026 21:08
d9cff31 to
fe15a70
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add --agent-clusters-per-instance. When greater than one, classifier deploys in the management cluster a single sveltos-agent Deployment for up to N clusters, instead of one Deployment per cluster. The clusters sharing a Deployment (a group) are recorded in a ConfigMap with the same name as the Deployment, using libsveltos agentgroup.
The flag applies only to agentless mode. It is ignored when the agent runs in the managed cluster, in pull mode, and when N is 1. The group Deployment is removed when its last member leaves, and members whose cluster is gone are removed by a periodic sweep. Only global agent patches apply to a group.
The agentless sveltos-agent Role gains access to configmaps.
Add unit tests and a post-merge FV job, FV_AGENTLESS_GROUPING, running make create-cluster-agentless-grouping fv-agentless-grouping.