Skip to content

Add fv test for drift detection of a Helm deployed custom resource in… - #2114

Merged
gianlucam76 merged 1 commit into
projectsveltos:release-1.17from
gianlucam76:release-1.17
Nov 20, 2026
Merged

gianlucam76 merged 1 commit into
projectsveltos:release-1.17from
gianlucam76:release-1.17

Conversation

@gianlucam76

Copy link
Copy Markdown
Member

… agentless mode (#2113)

When drift-detection-manager runs in the management cluster, the kinds deployed by Helm charts must be resolved against the managed cluster. If a chart deploys a custom resource with no namespace, and its CRD is only in the managed cluster, drift-detection-manager failed with "no matches for kind" and the ResourceSummary tracked nothing (helmResourceHashes stayed empty).

The test installs a cluster scoped CRD in the workload cluster only, deploys with ContinuousWithDriftDetection a Helm chart (bedag/raw) rendering an instance of it with no namespace, and verifies the ResourceSummary tracks that instance.

None of the existing specs could catch this: the ones going through Helm render only built-in kinds, or custom kinds with a namespace set, and the one with a CRD only in the managed cluster deploys through policyRefs, which never uses the REST mapper.

This PR also updates the drift-detection-manager which contains the fix

Fixes #2112

(cherry picked from commit cafc00c)

… agentless mode (projectsveltos#2113)

When drift-detection-manager runs in the management cluster, the kinds deployed by
Helm charts must be resolved against the managed cluster. If a chart deploys a custom
resource with no namespace, and its CRD is only in the managed cluster, drift-detection-manager
failed with "no matches for kind" and the ResourceSummary tracked nothing
(helmResourceHashes stayed empty).

The test installs a cluster scoped CRD in the workload cluster only, deploys with
ContinuousWithDriftDetection a Helm chart (bedag/raw) rendering an instance of it with no
namespace, and verifies the ResourceSummary tracks that instance.

None of the existing specs could catch this: the ones going through Helm render only
built-in kinds, or custom kinds with a namespace set, and the one with a CRD only in the
managed cluster deploys through policyRefs, which never uses the REST mapper.

This PR also updates the drift-detection-manager which contains the fix

Fixes projectsveltos#2112

(cherry picked from commit cafc00c)
@gianlucam76
gianlucam76 merged commit d68cf59 into projectsveltos:release-1.17 Nov 20, 2026
28 of 30 checks passed
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