Edit

Multi-cluster identity binding management with Azure Kubernetes Fleet Manager (preview)

Applies to: ✔️ Fleet Manager ✔️ Fleet Manager with hub cluster

Fleet Manager identity binding profiles let you centrally manage workload identity across multiple clusters.

Identity bindings for Azure Kubernetes Service (AKS) solve the scaling limitation of the existing workload identity feature by creating a single federated identity credential (FIC) per user-assigned managed identity (UAMI), allowing multiple AKS clusters to reuse the FIC. An identity binding maps one UAMI to one AKS cluster. If workloads on multiple clusters need to use the same UAMI, you need to create an identity binding for each cluster.

Identity binding profiles address this limitation by allowing you to define an identity binding once at the fleet level and distribute it across multiple clusters.

In this article, we introduce key concepts for managing identity bindings across multiple clusters by using Azure Kubernetes Fleet Manager and identity binding profiles.

Important

Azure Kubernetes Fleet Manager preview features are available on a self-service, opt-in basis. Previews are provided "as is" and "as available," and they're excluded from the service-level agreements and limited warranty. Azure Kubernetes Fleet Manager previews are partially covered by customer support on a best-effort basis. As such, these features aren't meant for production use.

Prerequisites and limitations

  • Member clusters must have workload identity and OIDC issuer enabled.
  • Member clusters configured with API server VNet integration aren't supported.
  • Arc-enabled Kubernetes clusters aren't supported.
  • An identity binding profile can authorize a maximum of 100 subjects.
  • Identity Binding properties (name and managed identity) can't be changed after creation.
  • Fleet Manager doesn't take over identity bindings that already exist on a member cluster.
  • Identity bindings configured and distributed by Fleet Manager can't be directly modified on member clusters.

What is an identity binding profile?

An identity binding profile defines the identity binding that each selected member cluster should have. It holds two things:

  • The managed identity that workloads use for Microsoft Entra token acquisition. Every selected cluster binds the same identity.
  • An optional list of allowed subjects defined by a JSON array of label selectors that match the namespaces and service accounts on the clusters that are authorized to use the identity.

Note

The allowedSubjects field of AKS Identity Binding is in preview.

If you omit this field, the system uses ClusterRole and ClusterRoleBinding objects on the member cluster for authorization, and you must define them manually. See authorize namespaces and service accounts. On a fleet with a hub cluster, you can distribute these objects to multiple clusters by using workload placement with a ClusterResourceEnvelope.

When you apply the identity binding profile, Fleet Manager creates and manages the identity binding resource on each selected member cluster by using the profile's configuration. Every selected cluster gets the same configuration.

Identity binding profiles select member clusters with member cluster labels in the same way resource placement does. Use the same labels for both so that your workloads target the clusters where the identity is configured. When you add a cluster to the selection, apply the profile and confirm that the binding is created before you place workloads on it.

Next steps