Azure-docs: Helm commands should be updated for v3

Created on 27 Nov 2019  Â·  14Comments  Â·  Source: MicrosoftDocs/azure-docs

Any mentions of tiller or helm init should be noted that they are only for pre-v3 of Helm.


Document Details

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

Pri1 application-gatewasvc assigned-to-author product-question triaged

Most helpful comment

Any update on this ? I am seeing the following error, when trying to helm3 install AGIC version

--version 1.2.0-rc1

`Error: unable to build kubernetes objects from release manifest: unable to recognize "":
no matches for kind "AzureIngressProhibitedTarget" in version "appgw.ingress.k8s.io/v1"

helm.go:84: [debug]
unable to recognize "": no matches for kind "AzureIngressProhibitedTarget" in version "appgw.ingress.k8s.io/v1"
unable to build kubernetes objects from release manifest`

Same here 😪

All 14 comments

@RobLSDev Thanks for your question. We are checking on this and will respond to you soon.

any news on when this will be updated?

Ack - currently testing Helm 3 myself and will update the docs accordingly + include a note that tiller and helm init only work for pre v3 Helm.

Hi Any update on helm 3?

[Proposal]

  • Not necessary for Helm v3
    helm init --tiller-namespace kube-system --service-account tiller-sa
  • Install command for Helm v3
    helm install -f application-gateway-kubernetes-ingress/ingress-azure --generate-name

[Similar documents]
https://docs.microsoft.com/en-us/azure/application-gateway/ingress-controller-install-existing#install-helm
https://docs.microsoft.com/en-us/azure/application-gateway/ingress-controller-install-new#install-helm
https://docs.microsoft.com/en-us/azure/terraform/terraform-create-k8s-cluster-with-aks-applicationgateway-ingress#install-ingress-controller-helm-chart

When using AGIC in shared mode with helm3, I got the error: info: skipping unknown hook: "crd-install"
It seems to be related to helm 3 not supporting crd-install hook.
https://github.com/Azure/application-gateway-kubernetes-ingress/issues/720
https://v3.helm.sh/docs/topics/charts_hooks/

Any update on this ? I am seeing the following error, when trying to helm3 install AGIC version

--version 1.2.0-rc1

`Error: unable to build kubernetes objects from release manifest: unable to recognize "":
no matches for kind "AzureIngressProhibitedTarget" in version "appgw.ingress.k8s.io/v1"

helm.go:84: [debug]
unable to recognize "": no matches for kind "AzureIngressProhibitedTarget" in version "appgw.ingress.k8s.io/v1"
unable to build kubernetes objects from release manifest`

Any update on this ? I am seeing the following error, when trying to helm3 install AGIC version

--version 1.2.0-rc1

`Error: unable to build kubernetes objects from release manifest: unable to recognize "":
no matches for kind "AzureIngressProhibitedTarget" in version "appgw.ingress.k8s.io/v1"

helm.go:84: [debug]
unable to recognize "": no matches for kind "AzureIngressProhibitedTarget" in version "appgw.ingress.k8s.io/v1"
unable to build kubernetes objects from release manifest`

Same here 😪

I managed to find a workaround for this. I was experiencing the same issue as most others using helm v3.

First I installed the chart with shared gateway set to false - so it actually deploys.

Then I created the CRD manually by modifying the templated version in the chart. This was my one: https://gist.github.com/brendanmckenzie/0ec8664686bdd936147c7406610e821b - the metadata.labels may differ for you.

I also updated the ingress-azure ConfigMap (name also may differ for you) to add APPGW_ENABLE_SHARED_APPGW: "true"

Then I rolled out a restart of the ingress kubectl rollout restart deployment/ingress-azure

And it was paying attention to my AzureIngressProhibitedTargets

I could see this in the logs of the ingress: mutate_app_gateway.go:78] [brownfield] Prohibited targets: ...

I am getting error with both standard and waf versions of application gateway-

1 main.go:193] App Gateway SKU Tier Standard is not supported by AGIC version 1.2.0-rc3/32ea3149/2020-06-05-07:50T+0000; (v0.10.0 supports App Gwy v1)

Hey @VipinAgarwal - AGIC only supports AppGW v2 SKUs (Standard_v2 and WAF_v2) beyond version 0.10.0. If you're using a version past 0.10.0 with an AppGW v1 SKU (Standard or WAF), then AGIC won't work.

Isthere any update on this? I'm still not able to deploy AGIC with shared: true with latest AGIC version.

Yes AGIC won't work with AppGW version v1(standard and WAF). You need to deploy AppGW v2 version then try AGIC 1.12.
Also, AGIC 1.10 won't deploy on AKS 1.16. Use 1.14 or before.

Regarding Updates from AGIC, I think currently its in process only. No implementation.

AKS 1.14 is not supported anymore since July. Furthermore this issue exists even with AKS 1.17 and AppGW v2.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

bityob picture bityob  Â·  3Comments

JamesDLD picture JamesDLD  Â·  3Comments

mrdfuse picture mrdfuse  Â·  3Comments

AronT-TLV picture AronT-TLV  Â·  3Comments

DeepPuddles picture DeepPuddles  Â·  3Comments