cloudacademy / aad-pod-identity

[DEPRECATED] Assign Azure Active Directory Identities to Kubernetes applications.

AAD Pod Identity

📣 Announcement

❗ IMPORTANT: As of Monday 10/24/2022, AAD Pod Identity is deprecated. As mentioned in the announcement, AAD Pod Identity has been replaced with Azure Workload Identity. Going forward, we will no longer add new features to this project in favor of Azure Workload Identity. We will continue to provide critical bug fixes until Azure Workload Identity reaches general availability. Following that, we will provide CVE patches until September 2023, at which time the project will be archived.

AAD Pod Identity enables Kubernetes applications to access cloud resources securely with Azure Active Directory.

Using Kubernetes primitives, administrators configure identities and bindings to match pods. Then without any code modifications, your containerized applications can leverage any resource in the cloud that depends on AAD as an identity provider.

Getting Started

Setup the correct role assignments on Azure and install AAD Pod Identity through Helm or YAML deployment files. Get familiar with our CRDs and core components.

Try our walkthrough to get a better understanding of the application workflow.

Release

Currently, AAD Pod Identity releases on a monthly basis to patch security vulnerabilities, targeting the first week of the month. Refer to Release Cadence for more details.

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information, see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

Support

aad-pod-identity is an open source project that is not covered by the Microsoft Azure support policy. Please search open issues here, and if your issue isn't already represented please open a new one. The project maintainers will respond to the best of their abilities.