Azure Kubernetes Service (AKS) and Managed Identity



Azure Kubernetes Service (AKS) cluster requires an identity to create additional resources like load balancers and managed disks in Azure. It can use a managed identity which AKS creates automatically. Azure Active Directory pod-managed identities uses Kubernetes primitives to associate managed identities for Azure resources and identities in Azure Active Directory (AAD) with pods. Administrators create identities and bindings as Kubernetes primitives that allow pods to access Azure resources that rely on AAD as an identity provider.
Download slide deck from here: https://nzpowerlunchfiles.blob.core.windows.net/data/aks-managed-identity-support-2020-01-15.pdf

source

4 thoughts on “Azure Kubernetes Service (AKS) and Managed Identity”
  1. this POD managed identity is in review stage? can we use it for production environment?

  2. Hi, I have some doubts.
    1. When I make a k8s cluster, azure creates a system assigned managed identify to it by default right? Can I use this to give k8s exclusive access to say – an image in blob storage?

    2. If we make a user assigned identity, can we tie it to the above mentioned aks cluster which already has the system assigned one?

Leave a Reply

Your email address will not be published.

Captcha loading...