Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: add note about pod identity deprecation #1018

Merged
merged 1 commit into from
Nov 10, 2022
Merged

docs: add note about pod identity deprecation #1018

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
12 changes: 6 additions & 6 deletions website/content/en/configurations/identity-access-modes/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,9 +11,9 @@ description: >

Following order of access modes is recommended for Secret Store CSI driver AKV provider:

| Access Option | Comment |
| ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Workload Identity (Preview) [**RECOMMENDED**] | This is currently in preview. It's a secure way to access Key Vault based on the [Workload Identity Federation](https://docs.microsoft.com/en-us/azure/active-directory/develop/workload-identity-federation). |
| Pod Identity | This is the most secure way to get access to Azure resources (AKV in this case) as it uses the managed identity bound to the Pod. |
| Managed Identities (System-assigned and User-assigned) | Managed identities eliminate the need for developers to manage credentials. Managed identities provide an identity for applications to use when connecting to Azure Keyvault. |
| Service Principal | This is the last option to consider while connecting to AKV as access credentials need to be created as Kubernetes Secret and stored in plain text in etcd. |
| Access Option | Comment |
| ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Workload Identity [**RECOMMENDED**] | This is the most secure way to access Key Vault based on the [Workload Identity Federation](https://docs.microsoft.com/en-us/azure/active-directory/develop/workload-identity-federation). |
| Pod Identity [**NOT RECOMMENDED**] | [AAD Pod Identity](https://github.com/Azure/aad-pod-identity) has been [DEPRECATED](https://github.com/Azure/aad-pod-identity#-announcement).<br>This provides a way to get access to Azure resources (AKV in this case) using the managed identity bound to the Pod.</br> |
| Managed Identities (System-assigned and User-assigned) | Managed identities eliminate the need for developers to manage credentials. Managed identities provide an identity for applications to use when connecting to Azure Keyvault. |
| Service Principal | This is the last option to consider while connecting to AKV as access credentials need to be created as Kubernetes Secret and stored in plain text in etcd. |
4 changes: 3 additions & 1 deletion website/content/en/configurations/identity-access-modes/pod-identity-mode.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
type: docs
title: "Pod Identity"
linkTitle: "Pod Identity"
weight: 2
weight: 4
description: >
Use Pod Identity to access Keyvault.
---
Expand Down Expand Up @@ -68,6 +68,8 @@ spec:

## Configure AAD Pod Identity to access Keyvault

> NOTE: [AAD Pod Identity](https://github.com/Azure/aad-pod-identity) has been [DEPRECATED](https://github.com/Azure/aad-pod-identity#-announcement). We recommend using [Workload Identity](../workload-identity-mode) instead.

**Prerequisites**

💡 Make sure you have installed pod identity to your Kubernetes cluster
Expand Down
2 changes: 1 addition & 1 deletion website/content/en/configurations/identity-access-modes/service-principal-mode.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
type: docs
title: "Service Principal"
linkTitle: "Service Principal"
weight: 1
weight: 3
description: >
Use a Service Principal to access Keyvault.
---
Expand Down
2 changes: 1 addition & 1 deletion ...ite/content/en/configurations/identity-access-modes/system-assigned-msi-mode.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
type: docs
title: "System-assigned Managed Identity"
linkTitle: "System-assigned Managed Identity"
weight: 4
weight: 2
description: >
Use a System-assigned Managed Identity to access Keyvault.
---
Expand Down
2 changes: 1 addition & 1 deletion website/content/en/configurations/identity-access-modes/user-assigned-msi-mode.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
type: docs
title: "User-assigned Managed Identity"
linkTitle: "User-assigned Managed Identity"
weight: 3
weight: 2
description: >
Use a User-assigned Managed Identity to access Keyvault.
---
Expand Down
2 changes: 1 addition & 1 deletion website/content/en/configurations/identity-access-modes/workload-identity-mode.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
type: docs
title: "Workload Identity (Preview)"
title: "Workload Identity"
linkTitle: "Workload Identity"
weight: 1
description: >
Expand Down