search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.27k stars 21.45k forks source link

Helm install command for cert-manager is incorrect #48681

Closed bmukes closed 4 years ago

bmukes commented 4 years ago

command should be updated as follows: helm install jetstack/cert-manager --namespace ingress-basic --version v0.13.1 --set ingressShim.defaultIssuerName=letsencrypt --set ingressShim.defaultIssuerKind=ClusterIssuer

Update required due to version number being different and also seems like Helm was updated in Azure Cloud Storage. This issue and issue #48675 also effects the documentation on the static ip address https://docs.microsoft.com/en-us/azure/aks/ingress-static-ip

Document Details

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

Karishma-Tiwari-MSFT commented 4 years ago

Thanks for the feedback! We are currently investigating and will update you shortly.

bmukes commented 4 years ago

I received the following letter from Microsoft Tech support this AM. Please close this issue.

Hi Brian, Thanks for your update. We are so sorry for the inconvenience. There was an error in the script which builds the cloud shell image. Helm released 2.16.3 more recently than 3.1 and the build script picked that up as the 'latest' release, causing the inadvertent downgrade. As helm v3 does not require tiller pod, so the tiller pod cannot be found when using helm v2. The helm version will be re-upgraded in the next release. As confirmed by you, the queries related to this issue have been solved and hence I will go ahead and archive your case at this time. Please remember that support for this case does not end here. Should you need further assistance with your issue, you can reach out to me and I will continue working with you.

Here is a summary of the key points of the case for your records.

Issue Definition: Helm install Error: could not find tiller.

Resolution/Suggestion Summary: You could refer to the follow the below document to configure helm V2: https://docs.microsoft.com/en-us/azure/aks/kubernetes-helm#install-an-application-with-helm-v2. Alternatively, you may also use the command below to upgrade the helm to version 3 as a workaround: curl https://aka.ms/cloud-shell-helm3 | bash. The command ‘helm version’ can be used to verify the version of Helm you have installed.

Besides, the syntax for helm 3 is different from helm 2. The syntax for helm v3 is ‘helm install [NAME] [CHART] [flags]’ while for hem v2 is ‘helm install [CHART] [flags]’. So you need to remove the word nginx after the word install if you are using helm v2. You could refer to the following document for more information: https://docs.microsoft.com/en-us/azure/aks/kubernetes-helm#install-an-application-with-helm-v2

It was my pleasure to work with you on this service request. Please do not hesitate to contact me if I can be of further assistance.

Thank you very much for your support of Microsoft Azure. Have a nice day😊!

Elaine Wang Best Regards

bmukes commented 4 years ago

I received the following letter from Microsoft Tech Support this AM so please close this Issue.

Hi Brian, Thanks for your update. We are so sorry for the inconvenience. There was an error in the script which builds the cloud shell image. Helm released 2.16.3 more recently than 3.1 and the build script picked that up as the 'latest' release, causing the inadvertent downgrade. As helm v3 does not require tiller pod, so the tiller pod cannot be found when using helm v2. The helm version will be re-upgraded in the next release. As confirmed by you, the queries related to this issue have been solved and hence I will go ahead and archive your case at this time. Please remember that support for this case does not end here. Should you need further assistance with your issue, you can reach out to me and I will continue working with you.

Here is a summary of the key points of the case for your records.

Issue Definition: Helm install Error: could not find tiller.

Resolution/Suggestion Summary: You could refer to the follow the below document to configure helm V2: https://docs.microsoft.com/en-us/azure/aks/kubernetes-helm#install-an-application-with-helm-v2. Alternatively, you may also use the command below to upgrade the helm to version 3 as a workaround: curl https://aka.ms/cloud-shell-helm3 | bash. The command ‘helm version’ can be used to verify the version of Helm you have installed.

Besides, the syntax for helm 3 is different from helm 2. The syntax for helm v3 is ‘helm install [NAME] [CHART] [flags]’ while for hem v2 is ‘helm install [CHART] [flags]’. So you need to remove the word nginx after the word install if you are using helm v2. You could refer to the following document for more information: https://docs.microsoft.com/en-us/azure/aks/kubernetes-helm#install-an-application-with-helm-v2

It was my pleasure to work with you on this service request. Please do not hesitate to contact me if I can be of further assistance.

Thank you very much for your support of Microsoft Azure. Have a nice day😊!

Elaine Wang Best Regards

BRIAN MUKES | Architect INSURANCE TECHNOLOGIES t: +1 719.442.6400 | f: +1 719.442.0600 [cid:image001.png@01D5EAF2.2899C910]https://www.insurancetechnologies.com/

From: Karishma Tiwari - MSFT notifications@github.com Sent: Friday, February 21, 2020 3:53 PM To: MicrosoftDocs/azure-docs azure-docs@noreply.github.com Cc: Mukes, Brian BMukes@InsuranceTechnologies.com; Author author@noreply.github.com Subject: Re: [MicrosoftDocs/azure-docs] Helm install command for cert-manager is incorrect (#48681)

Thanks for the feedback! We are currently investigating and will update you shortly.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/48681?email_source=notifications&email_token=AAU2RRLAGEGBUIPLFHZR5GLREBLLRA5CNFSM4KZIIYC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMULLOA#issuecomment-589870520, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAU2RRP6P5TKITK4WSC6KDDREBLLRANCNFSM4KZIIYCQ.

• Confidential and proprietary information may be contained in this communication, including attachments. If you are not the intended recipient, you must not use, copy, disclose, distribute or retain this communication or any part of it. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately by return e-mail and permanently delete this message and any attachments.