Skip to content

fix: remove a label key dropped from spec.classifierLabels - #518

Merged
gianlucam76 merged 1 commit into
projectsveltos:mainfrom
gianlucam76:bug-513
Sep 18, 2026
Merged

gianlucam76 merged 1 commit into
projectsveltos:mainfrom
gianlucam76:bug-513

Conversation

@gianlucam76

Copy link
Copy Markdown
Member

A key removed from spec.classifierLabels while a cluster still matches was never removed from that cluster. The updateLabelsOnCluster method only sets/updates keys currently in spec while registerMatchingClusters immediately drops this Classifier's ownership of the dropped key via RemoveStaleRegistrations, so no later pass could remove it either.

Fixes #513

A key removed from spec.classifierLabels while a cluster
still matches was never removed from that cluster. The
updateLabelsOnCluster method only sets/updates keys
currently in spec while registerMatchingClusters immediately
drops this Classifier's ownership of the dropped key via
RemoveStaleRegistrations, so no later pass could remove it
either.
@gianlucam76
gianlucam76 merged commit a6d616b into projectsveltos:main Sep 18, 2026
9 checks passed
@gianlucam76
gianlucam76 deleted the bug-513 branch September 18, 2026 19:50
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.

BUG: a label key removed from spec.classifierLabels is never removed from still-matching clusters

1 participant