Helm 3 multiple ingress controller install results in CRD conflict

[nick-cromwell]

Describe the bug
Trying to install two Ingress Controllers via Helm 3 results in the following error:

Error: rendered manifests contain a resource that already exists. Unable to continue with install: CustomResourceDefinition "virtualservers.k8s.nginx.org" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-name" must equal "test-internal-ingress": current value is "test-ingress"

To Reproduce
Steps to reproduce the behavior:

1. Start with a fresh cluster
2. Install an Ingress Controller and attempt to skip CRDs:
   helm install test-ingress nginx-stable/nginx-ingress --skip-crds
3. Attempt to install a second Ingress Controller:
   helm install test-internal-ingress nginx-stable/nginx-ingress --skip-crds
4. See error

Expected behavior
Two ingress controllers are installed with different release names

Your environment

• 1.16.8-gke.15
• GKE
• Using NGINX
• Helm 3.2.1

I believe I have worked around this by deleting the CRs between installs like so:
kubectl delete crd transportservers.k8s.nginx.org
kubectl delete crd virtualservers.k8s.nginx.org
kubectl delete crd virtualserverroutes.k8s.nginx.org

They were created again after installing the second ingress controller.

[Dean-Coakley]

Hi @nick-cromwell

Thanks for the bug report. This will be fixed soon.
This is a duplicate issue of #950.

Sorry for the inconvenience