Azure-docs: helm install install/kubernetes/helm/istio fails - customresourcedefinitions.apiextensions.k8s.io "reportnothings.config.istio.io" already exists

[nigel-dewar]

Error: release istio failed: customresourcedefinitions.apiextensions.k8s.io "reportnothings.config.istio.io" already exists

This is on a brand new kube cluster running in australiaeast. I had the same problem following instructions to install cert-manager. I had to do this to get around it

helm install --name cert-manager stable/cert-manager --namespace kube-system --set ingressShim.defaultIssuerName=letsencrypt-prod --set ingressShim.defaultIssuerKind=ClusterIssuer --set createCustomResource=false

helm upgrade --install --namespace kube-system  cert-manager stable/cert-manager --set createCustomResource=true

It seems the version of kube your running errors out, because it creates the customresourcedefinition too soon, and then errors out complaining that it already exists. pretty poor microsoft. I dont have this prob on GKE or AWS, or anywhere else for that matter.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 68b5d00d-529b-a8be-47bf-773c967f0e72
• Version Independent ID: 0cf044ef-b26f-a8fa-213f-1e3fffaf53d6
• Content: Install Istio in Azure Kubernetes Service (AKS)
• Content Source: articles/aks/istio-install.md
• Service: container-service
• GitHub Login: @paulbouwer
• Microsoft Alias: pabouwer

[jakaruna-MSFT]

@nigel-dewar Please let me know the version of helm you are using.
There is a known issue with helm version 2.12.0. Its creating crd's twice.
Refer to this pull request.
Solution is to move to the patch release(2.12.1). When you are migrating from previous versions to 2.12.1, Please checkout the comments in that pull request.

[jakaruna-MSFT]

@nigel-dewar you can also downgrade to 2.11.0 to avoid this issue.

20820 Check this issue for more details.

[nigel-dewar]

thank you jakaruna, it was the helm version, I changed to v 2.11 and issue is solved. thank you!

[jakaruna-MSFT]

@nigel-dewar Good to know that your issue is resolved.
I will close this out for now. If you need additional help please let me know and we can reopen and continue.