Cannot deploy same application in two different namespaces with kubernetes-external-secrets

[jonjesse]

We have an eks cluster with two namespaces, development and qa
We deploy same application in both namespaces.
The application deploys in development namespace successfully with the kubernetes-external-secrets working.
When we try to deploy the application in the qa namespace we get an error that Cluster role app-kubernetes-external-secrets exists and cannot be imported into the current release.
Below is the full message:

client.go:108: [debug] creating 1 resource(s)
install.go:141: [debug] CRD externalsecrets.kubernetes-client.io is already present. Skipping.
Error: rendered manifests contain a resource that already exists. Unable to continue with install: ClusterRole "app-kubernetes-external-secrets" 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 "app-qa": current value is "app-development"
helm.go:94: [debug] ClusterRole "app-kubernetes-external-secrets" 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 "app-qa": current value is "app-development"
rendered manifests contain a resource that already exists. Unable to continue with install

In the values file we use rbac create true.

[jonjesse]

I was able to resolve this with the:

fullnameOverride

option