Open jonathan-innis opened 3 years ago
I doubt changing targetNamespaces is supported by helm itself. Since helm releases are namespaced and locked to the namespace that they are deployed to, it might not be possible to move them to a new namespace.
This is an old issue but I suppose it holds true for helmv3 as well - https://github.com/helm/helm/issues/3657
We will eventually need Validating webhooks to prevent users from upgrading these fields.
@jonathan-innis Can we retry this with the migration to helm-controller?
Haven't tried this, need to track this as an item to attempt
When there is a change to the
spec.targetNamespace
is changed in the application group, the reconciler is unable to rollback the previous workflow as it can't find the previous one