Migrate Alloy from Monitoring Namespace to Its own Namespace

Migrate Alloy to its own namespace. How does upgrade work from migrating from monitoring namespace to its own (k8s-monitoring) intelligently on v1. Verify in dev cluster namespace migration process before moving to prod.

Helm Does Not Handle Namespace Changes Automatically • Helm tracks releases using release metadata, which is stored in the namespace where the release was first deployed. • When you change targetNamespace, Helm treats it as a new deployment, not a migration of existing resources. • The resources in the original namespace are not explicitly deleted, so they persist unless manually removed.

Flux and Helm Do Not Automatically Clean Up Old Resources • Flux applies the new HelmRelease configuration but does not perform an automatic cleanup of resources in the previous namespace. • This results in resources being duplicated across namespaces, with the old ones still existing unless explicitly removed.

Helm Release Metadata Remains in the Original Namespace • Helm stores release information in ConfigMaps or Secrets in the original namespace. • If targetNamespace is changed without a full uninstall (helm uninstall), Helm does not recognize that the old namespace’s resources should be deleted.