Ensure that your Azure Kubernetes Service (AKS) clusters are configured to use Microsoft Entra ID for authentication and Kubernetes Role-Based Access Control (Kubernetes native RBAC) for authorization. This allows secure, centralized identity management and fine-grained access control, reducing security risks and enabling better governance.
excellence
Interacting with the API server is essential for managing an Elastic Kubernetes Service (EKS) cluster. It is crucial to secure access to the API server and restrict it to authorized users only. Enabling Microsoft Entra ID with Kubernetes RBAC for an EKS cluster streamlines identity and access management by leveraging AAD's centralized authentication and RBAC capabilities. This type of integration enhances security, simplifies user management, and allows for consistent identity controls across both platforms, improving overall operational efficiency and reducing the complexity of managing access to the EKS cluster.
Audit
To determine if Microsoft Entra ID integration with Kubernetes RBAC is enabled for your AKS clusters, perform the following operations:
Remediation / Resolution
To enable Microsoft Entra ID integration with Kubernetes RBAC for your Azure Kubernetes Service (AKS) clusters, perform the following operations:
References
- Azure Official Documentation
- Access an Azure Kubernetes Service (AKS) API server
- Enable Azure managed identity authentication for Kubernetes clusters with kubelogin
- Enable Azure managed identity authentication for Kubernetes clusters with kubelogin
- Baseline architecture for an Azure Kubernetes Service (AKS) cluster
- Use Kubernetes role-based access control with Microsoft Entra ID in Azure Kubernetes Service
- Azure PowerShell Documentation
- az account list
- az account set
- az aks list
- az aks show
- az aks