Skip to content

Commit 2d90650

Browse files
Feedback
1 parent 7decfd3 commit 2d90650

File tree

1 file changed

+13
-53
lines changed

1 file changed

+13
-53
lines changed

articles/azure-app-configuration/quickstart-azure-kubernetes-service.md

Lines changed: 13 additions & 53 deletions
Original file line numberDiff line numberDiff line change
@@ -233,50 +233,22 @@ Add following key-values to the App Configuration store and leave **Label** and
233233
az aks get-credentials --name <your-aks-instance-name> --resource-group <your-aks-resource-group>
234234
```
235235
236-
2. Install Azure App Configuration Kubernetes Provider to your AKS cluster:
236+
1. Install Azure App Configuration Kubernetes Provider to your AKS cluster using `helm`:
237237
238-
#### [helm](#tab/helm)
239-
240-
Run the following command to install the helm chart.
241-
242238
```console
243239
helm install azureappconfiguration.kubernetesprovider \
244-
oci://mcr.microsoft.com/azure-app-configuration/helmchart/kubernetes-provider \
245-
--namespace azappconfig-system \
246-
--create-namespace
247-
```
248-
249-
#### [Azure CLI](#tab/cli)
250-
251-
Run the following commands to install the Azure App Configuration Kubernetes Provider as the [AKS extension](../aks/azure-app-configuration.md).
252-
253-
254-
1. Install the `k8s-extension` Azure CLI extension:
255-
256-
```azurecli
257-
az extension add --name k8s-extension
258-
```
259-
260-
2. Register the provider using the [az provider register](/cli/azure/provider#az-provider-register):
261-
262-
```azurecli
263-
az provider register --namespace Microsoft.KubernetesConfiguration
264-
```
265-
266-
3. Install the Azure App Configuration AKS extension:
267-
268-
```azurecli
269-
az k8s-extension create --cluster-type managedClusters \
270-
--cluster-name <your-aks-instance-name> \
271-
--resource-group <your-aks-resource-group> \
272-
--name appconfigurationkubernetesprovider \
273-
--extension-type Microsoft.AppConfiguration \
274-
--release-train preview
240+
oci://mcr.microsoft.com/azure-app-configuration/helmchart/kubernetes-provider \
241+
--namespace azappconfig-system \
242+
--create-namespace
275243
```
276244
277-
---
245+
> [!TIP]
246+
> 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+
>
278250
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.
280252
281253
```yaml
282254
apiVersion: azconfig.io/v1
@@ -304,7 +276,7 @@ Add following key-values to the App Configuration store and leave **Label** and
304276
> - 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.
305277
> - The ConfigMap will be deleted if the App Configuration Kubernetes Provider is uninstalled.
306278
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.
308280
309281
```yaml
310282
apiVersion: apps/v1
@@ -337,13 +309,13 @@ Add following key-values to the App Configuration store and leave **Label** and
337309
name: configmap-created-by-appconfig-provider
338310
```
339311
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.
341313
342314
```console
343315
kubectl apply -f ./Deployment -n appconfig-demo
344316
```
345317
346-
6. Refresh the browser. The page shows updated content.
318+
1. Refresh the browser. The page shows updated content.
347319
348320
![Screenshot showing Kubernetes Provider after using configMap.](./media/quickstarts/kubernetes-provider-app-launch-after.png)
349321
@@ -387,23 +359,11 @@ Use the logs for further troubleshooting. For example, if you see requests to yo
387359
## Clean up resources
388360

389361
Uninstall the App Configuration Kubernetes Provider from your AKS cluster if you want to keep the AKS cluster.
390-
### [helm](#tab/helm)
391362

392363
```console
393364
helm uninstall azureappconfiguration.kubernetesprovider --namespace azappconfig-system
394365
```
395366

396-
### [Azure CLI](#tab/cli)
397-
398-
```azurecli
399-
az k8s-extension delete --cluster-type managedClusters \
400-
--cluster-name <your-aks-instance-name> \
401-
--resource-group <your-aks-resource-group> \
402-
--name appconfigurationkubernetesprovider
403-
```
404-
405-
---
406-
407367
[!INCLUDE[Azure App Configuration cleanup](../../includes/azure-app-configuration-cleanup.md)]
408368

409369
> [!NOTE]

0 commit comments

Comments
 (0)