You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/aks/workload-identity-migrate-from-pod-identity.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ For either scenario, you need to have the federated trust setup before you updat
31
31
If your cluster is already using the latest version of the Azure Identity SDK, perform the following steps to complete the authentication configuration:
32
32
33
33
- Deploy workload identity in parallel to where the trust is setup. You can restart your application deployment to begin using the workload identity, where it injects the OIDC annotations into the application automatically.
34
-
- After verifying the application is able to authenticate successfully, you can [remove the pod-managed identity](remove-pod-managed-identity) annotations from your application and then remove the pod-managed identity add-on.
34
+
- After verifying the application is able to authenticate successfully, you can [remove the pod-managed identity](#remove-pod-managed-identity) annotations from your application and then remove the pod-managed identity add-on.
35
35
36
36
## Migrate from older version
37
37
@@ -40,12 +40,12 @@ If your cluster isn't using the latest version of the Azure Identity SDK, you ha
40
40
1. You can use a migration sidecar that we provide, which converts the IMDS transactions your application makes over to [OpenID Connect][openid-connect-overview] (OIDC). The migration sidecar isn't intended to be a long-term solution, but a way to get up and running quickly on workload identity. Running the migration sidecar within your application proxies the application IMDS transactions over to OIDC. Perform the following steps to:
41
41
42
42
-[Deploy the workload with migration sidecar](#deploy-the-workload-with-migration-sidecar) to proxy the application IMDS transactions.
43
-
- Once you verify the authentication transactions are completing successfully, you can [remove the pod-managed identity](remove-pod-managed-identity) annotations from your application and then remove the pod-managed identity add-on.
43
+
- Once you verify the authentication transactions are completing successfully, you can [remove the pod-managed identity](#remove-pod-managed-identity) annotations from your application and then remove the pod-managed identity add-on.
44
44
45
45
2. Rewrite your application to support the latest version of the [Azure Identity][azure-identity-supported-versions] client library. Afterwards, perform the following steps:
46
46
47
47
- Restart your application deployment to begin authenticating using the workload identity.
48
-
- Once you verify the authentication transactions are completing successfully, you can [remove the pod-managed identity](remove-pod-managed-identity) annotations from your application and then remove the pod-managed identity add-on.
48
+
- Once you verify the authentication transactions are completing successfully, you can [remove the pod-managed identity](#remove-pod-managed-identity) annotations from your application and then remove the pod-managed identity add-on.
0 commit comments