Azure / application-gateway-kubernetes-ingress

This is an ingress controller that can be run on Azure Kubernetes Service (AKS) to allow an Azure Application Gateway to act as the ingress for an AKS cluster.
https://azure.github.io/application-gateway-kubernetes-ingress
MIT License
668 stars 415 forks source link

Can we create deploy AGIC with just user assigned managed identity and without the pod identity? #1521

Open ankitrgupta1 opened 1 year ago

ankitrgupta1 commented 1 year ago

I'm trying to do a brownfield deployment of the AGIC on an AKS cluster with CNI networking.

However, since the pod identity/workload identity is in preview mode, we are not using it in our production.

I was wondering if I could deploy the AGIC using the user assigned managed identity alone?

I had been trying follow the below link https://learn.microsoft.com/en-us/azure/application-gateway/ingress-controller-install-existing

However instead of AAD pod identity I provided all the access using the user assigned managed identity.

Hence, while installing the AGIC as a helm chart using the step described here

https://learn.microsoft.com/en-us/azure/application-gateway/ingress-controller-install-existing

I get the following error:

Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: [resource mapping not found for name: "ingress-azure-1678735615" namespace: "" from "": no matches for kind "AzureIdentity" in version "aadpodidentity.k8s.io/v1" ensure CRDs are installed first, resource mapping not found for name: "ingress-azure-167811111" namespace: "" from "": no matches for kind "AzureIdentityBinding" in version "aadpodidentity.k8s.io/v1" ensure CRDs are installed first]

I was wondering if it is just because of the aad pod identity not enabled on the cluster.

If that is the case, and if I don't want to enable the pod identity, can I still be able to use AGIC?

Any help would be greatly appreciated.

ankitrgupta1 commented 1 year ago

Can we get an update on this?

bitsnorbytes commented 8 months ago

AAD Pod Identity is deprecated. You might want to use Azure Workload Identity

In the arm Auth Section of your config file. You might want to change to below

armAuth:
    type: workloadIdentity
    identityClientID:  <identityClientId>