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
> Besides using the `helm install`, you can also install Azure App Configuration Kubernetes Provider through [AKS extension](../aks/azure-app-configuration.md). There are two advantages:
247
+
> 1. The AKS extension is managed by Azure Resource Manager (ARM), you can use Azure CLI, ARM or bicep template to manage the installation.
248
+
> 1. The AKS extension supports automatic updates and version management, you don't have to manually manage the minor/patch version updates.
249
+
>
278
250
279
-
3. Add an *appConfigurationProvider.yaml* file to the *Deployment* directory with the following content to create an `AzureAppConfigurationProvider` resource. `AzureAppConfigurationProvider` is a custom resource that defines what data to download from an Azure App Configuration store and creates a ConfigMap.
251
+
1. Add an *appConfigurationProvider.yaml* file to the *Deployment* directory with the following content to create an `AzureAppConfigurationProvider` resource. `AzureAppConfigurationProvider` is a custom resource that defines what data to download from an Azure App Configuration store and creates a ConfigMap.
280
252
281
253
```yaml
282
254
apiVersion: azconfig.io/v1
@@ -304,7 +276,7 @@ Add following key-values to the App Configuration store and leave **Label** and
304
276
> - The ConfigMap will be reset based on the present data in your App Configuration store if it's deleted or modified by any other means.
305
277
> - The ConfigMap will be deleted if the App Configuration Kubernetes Provider is uninstalled.
306
278
307
-
4. Update the *deployment.yaml* file in the *Deployment* directory to use the ConfigMap `configmap-created-by-appconfig-provider` as a mounted data volume. It is important to ensure that the `volumeMounts.mountPath` matches the `WORKDIR` specified in your *Dockerfile* and the *config* directory created before.
279
+
1. Update the *deployment.yaml* file in the *Deployment* directory to use the ConfigMap `configmap-created-by-appconfig-provider` as a mounted data volume. It is important to ensure that the `volumeMounts.mountPath` matches the `WORKDIR` specified in your *Dockerfile* and the *config* directory created before.
308
280
309
281
```yaml
310
282
apiVersion: apps/v1
@@ -337,13 +309,13 @@ Add following key-values to the App Configuration store and leave **Label** and
337
309
name: configmap-created-by-appconfig-provider
338
310
```
339
311
340
-
5. Run the following command to deploy the changes. Replace the namespace if you are using your existing AKS application.
312
+
1. Run the following command to deploy the changes. Replace the namespace if you are using your existing AKS application.
341
313
342
314
```console
343
315
kubectl apply -f ./Deployment -n appconfig-demo
344
316
```
345
317
346
-
6. Refresh the browser. The page shows updated content.
318
+
1. Refresh the browser. The page shows updated content.
347
319
348
320

349
321
@@ -387,23 +359,11 @@ Use the logs for further troubleshooting. For example, if you see requests to yo
387
359
## Clean up resources
388
360
389
361
Uninstall the App Configuration Kubernetes Provider from your AKS cluster if you want to keep the AKS cluster.
0 commit comments