Note able to deploy on more than one k8s namespace

[k-p-ani]

What did you do to encounter the bug? Steps to reproduce the behavior:

1. Create a namespace test-1 in k8s cluster
2. Deploy the chart using helm in the namespace test-1.
3. Create another namespace test-2 in the same k8s cluster
4. Deploy the chart using helm in the namespace test-2 .

What did you expect? expected that deployment happen properly in both the namespace.

What happened instead? First deployment which was done on namespace test-1, was successfully. Second deployment on namespace test-2 failed with below message

INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: CustomResourceDefinition "mongodbcommunity.mongodbcommunity.mongodb.com" 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 "test-2": current value is "test-1"

Kubernetes Cluster Information

• Distribution ranchor
• Version 1.21

[github-actions[bot]]

This issue is being marked stale because it has been open for 60 days with no activity. Please comment if this issue is still affecting you. If there is no change, this issue will be closed in 30 days.

[github-actions[bot]]

This issue was closed because it became stale and did not receive further updates. If the issue is still affecting you, please re-open it, or file a fresh Issue with updated information.