Skip to content

Commit 59dbe96

Browse files
committed
fixed link issue
1 parent f445565 commit 59dbe96

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/aks/workload-identity-migrate-from-pod-identity.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ For either scenario, you need to have the federated trust setup before you updat
3131
If your cluster is already using the latest version of the Azure Identity SDK, perform the following steps to complete the authentication configuration:
3232

3333
- 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.
3535

3636
## Migrate from older version
3737

@@ -40,12 +40,12 @@ If your cluster isn't using the latest version of the Azure Identity SDK, you ha
4040
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:
4141

4242
- [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.
4444

4545
2. Rewrite your application to support the latest version of the [Azure Identity][azure-identity-supported-versions] client library. Afterwards, perform the following steps:
4646

4747
- 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.
4949

5050
## Create a managed identity
5151

0 commit comments

Comments
 (0)