@@ -172,7 +172,6 @@ by setting the `AZURE_CLIENT_ID` environment variable in the source-controller d
172
172
If you are running into further issues, please look at the
173
173
[troubleshooting guide](https://github.com/Azure/azure-sdk-for-go/blob/main/sdk/azidentity/TROUBLESHOOTING.md#azure-virtual-machine-managed-identity).
174
174
175
-
176
175
# #### Workload Identity
177
176
178
177
When using Workload Identity to enable access to ACR, add the following patch to
@@ -210,7 +209,7 @@ patches:
210
209
azure.workload.identity/use: "true"
211
210
` ` `
212
211
213
- Ensure Workload Identity is properly setup on your cluster and the mutating webhook is installed.
212
+ Ensure Workload Identity is properly set up on your cluster and the mutating webhook is installed.
214
213
Create an identity that has access to ACR. Next, establish
215
214
a federated identity between the source-controller ServiceAccount and the
216
215
identity. Patch the source-controller Deployment and ServiceAccount as shown in the patch
@@ -221,7 +220,6 @@ above. Please take a look at this [guide](https://azure.github.io/azure-workload
221
220
**Note:** The AAD Pod Identity project will be archived in [September 2023](https://github.com/Azure/aad-pod-identity#-announcement),
222
221
and you are advised to use Workload Identity instead.
223
222
224
-
225
223
When using aad-pod-identity to enable access to ACR, add the following patch to
226
224
your bootstrap repository, in the `flux-system/kustomization.yaml` file :
227
225
@@ -246,7 +244,7 @@ has to be used to give the `source-controller` pod access to the ACR.
246
244
To do this, you have to install `aad-pod-identity` on your cluster, create a managed identity
247
245
that has access to the container registry (this can also be the Kubelet identity
248
246
if it has `AcrPull` role assignment on the ACR), create an `AzureIdentity` and `AzureIdentityBinding`
249
- that describe the managed identity and then label the `source-controller` pods
247
+ that describe the managed identity and then label the `source-controller` deployment
250
248
with the name of the AzureIdentity as shown in the patch above. Please take a look
251
249
at [this guide](https://azure.github.io/aad-pod-identity/docs/) or
252
250
[this one](https://docs.microsoft.com/en-us/azure/aks/use-azure-ad-pod-identity)
0 commit comments