Skip to content

feat: honor IncludeDeletingResources in ManagementClusterClassifier matching - #512

Merged
gianlucam76 merged 1 commit into
projectsveltos:mainfrom
gianlucam76:bug-1970
Sep 16, 2026
Merged

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

Conversation

@gianlucam76

Copy link
Copy Markdown
Member

fetchResourcesForSelector always excluded any resource with a non-zero metadata.deletionTimestamp before evaluation.
This made it impossible to classify/react based on a resource while it is being deleted but still exists.

libsveltos now has an opt-in ResourceSelector.IncludeDeletingResources field (default false). This PR makes mgmtcluster_classifier_utils.go` honor it, matching the equivalent fix already made in sveltos-agent.

This PR also advances sveltos-agent images which contain same change for classifier, eventSource and healthCheck resource selection.

Part of 1970

…atching

`fetchResourcesForSelector` always excluded any resource with a non-zero
`metadata.deletionTimestamp` before evaluation.
This made it impossible to classify/react based on a resource while it is
being deleted but still exists.

libsveltos now has an opt-in `ResourceSelector.IncludeDeletingResources`
field (default `false). This PR makes `mgmtcluster_classifier_utils.go`
honor it, matching the equivalent fix already made in sveltos-agent.

This PR also advances sveltos-agent images which contain same change
for classifier, eventSource and healthCheck resource selection.

Part of
@gianlucam76
gianlucam76 merged commit ba9a8f2 into projectsveltos:main Sep 16, 2026
9 checks passed
@gianlucam76
gianlucam76 deleted the bug-1970 branch September 16, 2026 11:52
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