Merge pull request #261843 from zhenlan/k8s-provider

Add best practice for AKS

Author: AnnaMHuff

articles/azure-app-configuration/TOC.yml

@@ -41,12 +41,12 @@
           href: quickstart-feature-flag-azure-functions-csharp.md
     - name: Service integration
       items:
-        - name: Azure Container Apps
-          href: quickstart-container-apps.md
-        - name: App Service & Azure Functions
-          href: /azure/app-service/app-service-configuration-references
         - name: Azure Kubernetes Service
           href: quickstart-azure-kubernetes-service.md
+        - name: App Service & Azure Functions
+          href: /azure/app-service/app-service-configuration-references
+        - name: Azure Container Apps
+          href: quickstart-container-apps.md
     - name: Deployment
       items:
         - name: Bicep

articles/azure-app-configuration/howto-best-practices.md

@@ -9,7 +9,7 @@ editor: ''
 ms.assetid: 
 ms.service: azure-app-configuration
 ms.topic: conceptual
-ms.date: 09/08/2023
+ms.date: 12/21/2023
 ms.author: zhenlwa
 ms.custom: "devx-track-csharp, mvc"
 ---
@@ -67,6 +67,16 @@ To access an App Configuration store, you can use its connection string, which i
 
 A better option is to use the managed identities feature in Microsoft Entra ID. With managed identities, you need only the App Configuration endpoint URL to bootstrap access to your App Configuration store. You can embed the URL in your application code (for example, in the *appsettings.json* file). See [Use managed identities to access App Configuration](howto-integrate-azure-managed-service-identity.md) for details.
 
+## Azure Kubernetes Service access to App Configuration
+
+The following options are available for workloads hosted in Azure Kubernetes Service (AKS) to access Azure App Configuration. These options also apply to Kubernetes in general.
+
+* **Add [Azure App Configuration Kubernetes Provider](./quickstart-azure-kubernetes-service.md) to your AKS cluster.** The Kubernetes provider runs as a pod in the cluster. It can construct ConfigMaps and Secrets from key-values and Key Vault references in your App Configuration store. The ConfigMap and Secret are consumable as environment variables or mounted files without requiring any modifications to your application code. If you have multiple applications running in the same AKS cluster, they can all access the generated ConfigMaps and Secrets, eliminating the need for individual requests to App Configuration. The Kubernetes provider also supports dynamic configuration updates. This is the recommended option if feasible for you.
+
+* **Update your application to use Azure App Configuration provider libraries.** The provider libraries are available in many frameworks and languages, such as [ASP.NET](./quickstart-aspnet-core-app.md), [.NET](./quickstart-dotnet-core-app.md), [Java Spring](./quickstart-java-spring-app.md), [JavaScript/Node.js](./quickstart-javascript-provider.md), and [Python](./quickstart-python-provider.md). This approach gives you full access to App Configuration's functionalities, including dynamic configuration and feature management. You have granular control of what data to load and from which App Configuration store for each application.
+
+* **[Integrate with Kubernetes deployment using Helm](./integrate-kubernetes-deployment-helm.md).** If you do not wish to update your application or add a new pod to your AKS cluster, you have the option of bringing data from App Configuration to your Kubernetes cluster by using Helm via deployment. This approach enables your application to continue accessing configuration from Kubernetes variables and Secrets. You can run Helm upgrade whenever you want your application to incorporate new configuration changes.
+
 ## App Service or Azure Functions access to App Configuration
 
 Use the App Configuration provider or SDK libraries to access App Configuration directly in your application. This approach gives you full access to App Configuration's functionalities, including dynamic configuration and feature management. Your application running on App Service or Azure Functions can obtain access to your App Configuration store via any of the following methods: