Clean up orphaned sveltos-agent version ConfigMaps - #503
Merged
gianlucam76 merged 1 commit intoAug 30, 2026
Conversation
removeSveltosAgentFromManagementCluster tears down every resource in the sveltos-agent manifest for a cluster that's gone, but never touched the sa-* version ConfigMap since that gets written by the running agent itself, not deployed as part of the manifest. Left unowned and never cleaned up, these accumulate without bound - one NKS cell had ~2000 of them from nothing but a canary probe's create/delete cycle. Delete it last, after every manifest resource (including the deployment) already has a delete issued, and propagate the error instead of swallowing it like the rest of that function does: cleanClusterStaleResources turns a failure here into a requeue, so this gets retried through both the reconciler and the periodic sweep instead of just giving up.
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
2 participants
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.
removeSveltosAgentFromManagementCluster tears down every resource in the sveltos-agent manifest for a cluster that's gone, but never touched the sa-* version ConfigMap since that gets written by the running agent itself, not deployed as part of the manifest. Left unowned and never cleaned up, these accumulate without bound - one NKS cell had ~2000 of them from nothing but a canary probe's create/delete cycle.
Delete it last, after every manifest resource (including the deployment) already has a delete issued, and propagate the error instead of swallowing it like the rest of that function does: cleanClusterStaleResources turns a failure here into a requeue, so this gets retried through both the reconciler and the periodic sweep instead of just giving up.