Skip to content

Commit 8f26bac

Browse files
committed
Fix indents
1 parent d236b7e commit 8f26bac

File tree

1 file changed

+49
-49
lines changed

1 file changed

+49
-49
lines changed

AKS-Hybrid/aks-edge-workload-identity.md

Lines changed: 49 additions & 49 deletions
Original file line numberDiff line numberDiff line change
@@ -159,71 +159,71 @@ The following example shows how to use the Azure role-based access control (Azur
159159

160160
1. Create a key vault with purge protection and RBAC authorization enabled. You can also use an existing key vault if it is configured for both purge protection and RBAC authorization:
161161

162-
```azurecli
163-
az keyvault create --name $KVName --resource-group $resource_group_name --location $Location --enable-purge-protection --enable-rbac-authorization
162+
```azurecli
163+
az keyvault create --name $KVName --resource-group $resource_group_name --location $Location --enable-purge-protection --enable-rbac-authorization
164164
165-
# retrieve the key vault ID for role assignment
166-
$KVId=$(az keyvault show --resource-group $resource_group_name --name $KVName --query id --output tsv)
167-
```
165+
# retrieve the key vault ID for role assignment
166+
$KVId=$(az keyvault show --resource-group $resource_group_name --name $KVName --query id --output tsv)
167+
```
168168

169169
1. Assign the RBAC [Key Vault Secrets Officer](/azure/role-based-access-control/built-in-roles/security#key-vault-secrets-officer) role to yourself so that you can create a secret in the new key vault. New role assignments can take up to five minutes to propagate and be updated by the authorization server.
170170

171-
```azurecli
172-
az role assignment create --assignee-object-id $MSIPrincipalId --role "Key Vault Secrets Officer" --scope $KVId --assignee-principal-type ServicePrincipal
173-
```
171+
```azurecli
172+
az role assignment create --assignee-object-id $MSIPrincipalId --role "Key Vault Secrets Officer" --scope $KVId --assignee-principal-type ServicePrincipal
173+
```
174174

175175
1. Create a secret in the key vault:
176176

177-
```azurecli
178-
az keyvault secret set --vault-name $KVName --name $KVSecretName --value "Hello!"
179-
```
177+
```azurecli
178+
az keyvault secret set --vault-name $KVName --name $KVSecretName --value "Hello!"
179+
```
180180

181181
1. Assign the [Key Vault Secrets User](/azure/role-based-access-control/built-in-roles/security#key-vault-secrets-user) role to the user-assigned managed identity that you created previously. This step gives the managed identity permission to read secrets from the key vault:
182182

183-
```azurecli
184-
az role assignment create --assignee-object-id $MSIPrincipalId --role "Key Vault Secrets User" --scope $KVId --assignee-principal-type ServicePrincipal
185-
```
183+
```azurecli
184+
az role assignment create --assignee-object-id $MSIPrincipalId --role "Key Vault Secrets User" --scope $KVId --assignee-principal-type ServicePrincipal
185+
```
186186

187187
1. Create an environment variable for the key vault URL:
188188

189-
```azurecli
190-
$KVUrl=$(az keyvault show --resource-group $resource_group_name --name $KVName --query properties.vaultUri --output tsv)
191-
```
189+
```azurecli
190+
$KVUrl=$(az keyvault show --resource-group $resource_group_name --name $KVName --query properties.vaultUri --output tsv)
191+
```
192192

193193
1. Deploy a pod that references the service account and key vault URL:
194194

195-
```azurecli
196-
$yaml = @"
197-
apiVersion: v1
198-
kind: Pod
199-
metadata:
200-
name: sample-quick-start
201-
namespace: $SERVICE_ACCOUNT_NAMESPACE
202-
labels:
203-
azure.workload.identity/use: "true"
204-
spec:
205-
serviceAccountName: $SERVICE_ACCOUNT_NAME
206-
containers:
207-
- image: ghcr.io/azure/azure-workload-identity/msal-go
208-
name: oidc
209-
env:
210-
- name: KEYVAULT_URL
211-
value: $KVUrl
212-
- name: SECRET_NAME
213-
value: $KVSecretName
214-
nodeSelector:
215-
kubernetes.io/os: linux
216-
"@
217-
218-
# Replace variables within the YAML content
219-
$yaml = $yaml -replace '\$SERVICE_ACCOUNT_NAMESPACE', $SERVICE_ACCOUNT_NAMESPACE `
220-
-replace '\$SERVICE_ACCOUNT_NAME', $SERVICE_ACCOUNT_NAME `
221-
-replace '\$KVUrl', $KVUrl `
222-
-replace '\$KVSecretName', $KVSecretName
223-
224-
# Apply the YAML configuration
225-
$yaml | kubectl --kubeconfig $aks_cluster_name apply -f -
226-
```
195+
```azurecli
196+
$yaml = @"
197+
apiVersion: v1
198+
kind: Pod
199+
metadata:
200+
name: sample-quick-start
201+
namespace: $SERVICE_ACCOUNT_NAMESPACE
202+
labels:
203+
azure.workload.identity/use: "true"
204+
spec:
205+
serviceAccountName: $SERVICE_ACCOUNT_NAME
206+
containers:
207+
- image: ghcr.io/azure/azure-workload-identity/msal-go
208+
name: oidc
209+
env:
210+
- name: KEYVAULT_URL
211+
value: $KVUrl
212+
- name: SECRET_NAME
213+
value: $KVSecretName
214+
nodeSelector:
215+
kubernetes.io/os: linux
216+
"@
217+
218+
# Replace variables within the YAML content
219+
$yaml = $yaml -replace '\$SERVICE_ACCOUNT_NAMESPACE', $SERVICE_ACCOUNT_NAMESPACE `
220+
-replace '\$SERVICE_ACCOUNT_NAME', $SERVICE_ACCOUNT_NAME `
221+
-replace '\$KVUrl', $KVUrl `
222+
-replace '\$KVSecretName', $KVSecretName
223+
224+
# Apply the YAML configuration
225+
$yaml | kubectl --kubeconfig $aks_cluster_name apply -f -
226+
```
227227

228228
## Step 3: Deploy your application
229229

0 commit comments

Comments
 (0)