Skip to content

Commit f592ddf

Browse files
Merge pull request #273493 from RichardChen820/appconfig/junbchen/azd
[AzAppConfig] Introduce AZD template in K8s provider quickstart
2 parents 77233d1 + 4f58e6d commit f592ddf

File tree

1 file changed

+16
-6
lines changed

1 file changed

+16
-6
lines changed

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

Lines changed: 16 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.service: azure-app-configuration
77
ms.devlang: csharp
88
ms.custom: devx-track-csharp, mode-other
99
ms.topic: quickstart
10-
ms.date: 02/20/2024
10+
ms.date: 04/24/2024
1111
ms.author: junbchen
1212
#Customer intent: As an Azure Kubernetes Service user, I want to manage all my app settings in one place using Azure App Configuration.
1313
---
@@ -20,6 +20,16 @@ A ConfigMap can be consumed as environment variables or a mounted file. In this
2020

2121
> [!TIP]
2222
> See [options](./howto-best-practices.md#azure-kubernetes-service-access-to-app-configuration) for workloads hosted in Kubernetes to access Azure App Configuration.
23+
>
24+
25+
> [!NOTE]
26+
> This quickstart will walk you through setting up the Azure App Configuration Kubernetes Provider. Optionally, you can use the following [Azure Developer CLI](/azure/developer/azure-developer-cli/install-azd) commands with the `azure-appconfig-aks` template to provision Azure resources and deploy the sample application used by this quickstart. For more information about this template, visit the [azure-appconfig-aks](https://github.com/Azure-Samples/azure-appconfig-aks) repo on GitHub.
27+
>
28+
> ``` azd
29+
> azd init -t azure-appconfig-aks
30+
> azd up
31+
> ```
32+
>
2333
2434
## Prerequisites
2535
@@ -32,10 +42,6 @@ A ConfigMap can be consumed as environment variables or a mounted file. In this
3242
* [helm](https://helm.sh/docs/intro/install/)
3343
* [kubectl](https://kubernetes.io/docs/tasks/tools/)
3444
35-
> [!TIP]
36-
> The Azure Cloud Shell is a free, interactive shell that you can use to run the command line instructions in this article. It has common Azure tools preinstalled, including the .NET Core SDK. If you're logged in to your Azure subscription, launch your [Azure Cloud Shell](https://shell.azure.com) from shell.azure.com. You can learn more about Azure Cloud Shell by [reading our documentation](../cloud-shell/overview.md)
37-
>
38-
3945
## Create an application running in AKS
4046
4147
In this section, you will create a simple ASP.NET Core web application running in Azure Kubernetes Service (AKS). The application reads configuration from a local JSON file. In the next section, you will enable it to consume configuration from Azure App Configuration without changing the application code. If you already have an AKS application that reads configuration from a file, skip this section and go to [Use App Configuration Kubernetes Provider](#use-app-configuration-kubernetes-provider). You only need to ensure the configuration file generated by the provider matches the file path used by your application.
@@ -306,7 +312,7 @@ Add following key-values to the App Configuration store and leave **Label** and
306312
307313
![Screenshot showing Kubernetes Provider after using configMap.](./media/quickstarts/kubernetes-provider-app-launch-after.png)
308314
309-
### Troubleshooting
315+
## Troubleshooting
310316
311317
If you don't see your application picking up the data from your App Configuration store, run the following command to validate that the ConfigMap is created properly.
312318
@@ -353,6 +359,10 @@ helm uninstall azureappconfiguration.kubernetesprovider --namespace azappconfig-
353359

354360
[!INCLUDE[Azure App Configuration cleanup](../../includes/azure-app-configuration-cleanup.md)]
355361

362+
> [!NOTE]
363+
> If you use the Azure Developer CLI to set up the resources, you can run the `azd down` command to delete all resources created by the `azure-appconfig-aks` template.
364+
>
365+
356366
## Next steps
357367

358368
In this quickstart, you:

0 commit comments

Comments
 (0)