Helm install fails if same release name is used in two different namespaces

[Prafull Ladha]

Right now if you install cockroachdb in two different namespace with same release name. The first install is successful.

prafulll@18004 helm-charts % helm install crdb ./cockroachdb -n crdb-1
NAME: crdb
LAST DEPLOYED: Tue Mar 21 22:34:23 2023
NAMESPACE: crdb-1
STATUS: deployed
REVISION: 1
NOTES:
CockroachDB can be accessed via port 26257 at the
following DNS name from within your cluster:

crdb-cockroachdb-public.crdb-1.svc.cluster.local

Because CockroachDB supports the PostgreSQL wire protocol, you can connect to
the cluster using any available PostgreSQL client.

Note that because the cluster is running in secure mode, any client application
that you attempt to connect will either need to have a valid client certificate
or a valid username and password.

Finally, to open up the CockroachDB admin UI, you can port-forward from your
local machine into one of the instances in the cluster:

    kubectl port-forward crdb-cockroachdb-0 8080

Then you can access the admin UI at https://localhost:8080/ in your web browser.

For more information on using CockroachDB, please see the project's docs at:
https://www.cockroachlabs.com/docs/

Second install fails with following error:

prafulll@18004 helm-charts % helm install crdb ./cockroachdb -n crdb-2
Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: ClusterRole "crdb-cockroachdb" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-namespace" must equal "crdb-2": current value is "crdb-1"