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
When using Workload Identity to enable access to ACR, add the following patch to
@@ -270,13 +276,15 @@ patches:
270
276
azure.workload.identity/use: "true"
271
277
```
272
278
273
-
To use Workload Identity, you have to install the Workload Identity
274
-
mutating webhook and create an identity that has access to ACR. Next, establish
279
+
To use Workload Identity, the Workload Identity mutating webhook has to be installed on your cluster and
280
+
you have to create an identity that has access to ACR. Next, establish
275
281
a federated identity between the source-controller ServiceAccount and the
276
282
identity. Patch the source-controller Pod and ServiceAccount as shown in the patch
277
283
above. Please take a look at this [guide](https://azure.github.io/azure-workload-identity/docs/quick-start.html#6-establish-federated-identity-credential-between-the-identity-and-the-service-account-issuer--subject).
278
284
279
-
##### AAD Pod Identity
285
+
##### Deprecated: AAD Pod Identity
286
+
287
+
**Note:** AAD Pod Identity will be archived in September 2023, and you are advised to use Workload Identity instead.
280
288
281
289
When using aad-pod-identity to enable access to ACR, add the following patch to
282
290
your bootstrap repository, in the `flux-system/kustomization.yaml` file:
0 commit comments