Alternative location for Drift Detection Resources

[sim500]

Is your feature request related to a problem? Please describe.
We use Kamaji to deploy dedicated downstream clusters and rely on Sveltos with syncMode: ContinuousWithDriftDetection to ensure critical infrastructure resources remain intact. Currently, drift detection requires creating a projectsveltos namespace on each downstream cluster, which contains a ConfigMap tracking drift. If this namespace or its resources are deleted, drift detection stops working.

This setup poses a challenge because it exposes internal system components to customers, increasing the risk of accidental deletion and potential disruptions.

Describe the solution you'd like
We would like an option to manage drift detection entirely within the management cluster, avoiding the need to create a projectsveltos namespace on the downstream cluster.

Describe alternatives you've considered

• Manage drift detection within the management cluster instead of creating a namespace on the downstream cluster.
• Allow tracking drift state in a different location, such a configurable namespace.
• Use annotations on existing permanent resources instead of a separate ConfigMap.

Additional context
Minimizing the visibility of these resources to customers would enhance the reliability of drift detection while reducing the risk of accidental interference.

Thanks for your consideration!