Merge pull request #299755 from linglingye001/k8sprovider/refreshAll

Update k8s provider refresh example

Author: prmerger-automator[bot]

articles/azure-app-configuration/enable-dynamic-configuration-azure-kubernetes-service.md

@@ -23,22 +23,9 @@ If you use Azure Kubernetes Service (AKS), this tutorial shows you how to enable
 
 Finish the quickstart: [Use Azure App Configuration in Azure Kubernetes Service](./quickstart-azure-kubernetes-service.md).
 
-> [!TIP]
-> 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).
->
-## Add a sentinel key
-
-A *sentinel key* is a key that you update after you complete the change of all other keys. Your app monitors the sentinel key. When a change is detected, your app refreshes all configuration values. This approach helps to ensure the consistency of configuration in your app and reduces the overall number of requests made to your App Configuration store, compared to monitoring all keys for changes.
-
-Add the following key-value to your App Configuration store. For more information about how to add key-values to a store using the Azure portal or the CLI, go to [Create a key-value](./quickstart-azure-app-configuration-create.md#create-a-key-value).
-
-| Key | Value |
-|---|---|
-| Settings:Sentinel | 1 |
-
 ## Reload data from App Configuration
 
-1. Open the *appConfigurationProvider.yaml* file located in the *Deployment* directory. Then, add the `refresh` section under the `configuration` property. It enables configuration refresh by monitoring the sentinel key.
+1. Open the *appConfigurationProvider.yaml* file located in the *Deployment* directory. Then, add the `refresh` section under the `configuration` property. It enables the Kubernetes provider to reload the entire configuration whenever it detects a change in any of the selected key-values (those starting with *Settings:* and having no label). For more information about monitoring configuration changes, see [Best practices for configuration refresh](./howto-best-practices.md#configuration-refresh).
 
     ```yaml
     apiVersion: azconfig.io/v1
@@ -58,13 +45,10 @@ Add the following key-value to your App Configuration store. For more informatio
       configuration:
         refresh:
           enabled: true
-          monitoring:
-            keyValues:
-            - key: Settings:Sentinel
     ```
 
     > [!TIP]
-    > By default, the Kubernetes provider polls the monitoring key-values every 30 seconds for change detection. However, you can change this behavior by setting the `interval` property of the `refresh`. If you want to reduce the number of requests to your App Configuration store, you can adjust it to a higher value.
+    > You can set the `interval` property of the `refresh` to specify the minimum time between configuration refreshes. In this example, you use the default value of 30 seconds. Adjust to a higher value if you need to reduce the number of requests made to your App Configuration store.
 
 1. Open the *deployment.yaml* file in the *Deployment* directory and add the following content to the `spec.containers` section. Your application loads configuration from a volume-mounted file the App Configuration Kubernetes provider generates. By setting this environment variable, your application can [use polling to monitor changes in mounted files](/dotnet/api/microsoft.extensions.fileproviders.physicalfileprovider.usepollingfilewatcher).
 
@@ -90,7 +74,6 @@ Add the following key-value to your App Configuration store. For more informatio
     | Key | Value |
     |---|---|
     | Settings:Message | Hello from Azure App Configuration - now with live updates! |
-    | Settings:Sentinel | 2 |
 
 1. After refreshing the browser a few times, you'll see the updated content once the ConfigMap is updated in 30 seconds.
 

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

@@ -84,6 +84,24 @@ const appConfig = await load(endpoint, credential, {
 });
 ```
 
+#### [Kubernetes](#tab/kubernetes)
+
+```yaml
+apiVersion: azconfig.io/v1
+kind: AzureAppConfigurationProvider
+metadata:
+  name: appconfigurationprovider-sample
+spec:
+  endpoint: <your-app-configuration-store-endpoint>
+  target:
+    configMapName: configmap-created-by-appconfig-provider
+  configuration:
+    selectors:
+      - keyFilter: TestApp*
+    refresh:
+      enabled: true
+```
+
 ---
 
 ### Monitoring a sentinel key
@@ -118,6 +136,27 @@ const appConfig = await load(endpoint, credential, {
 });
 ```
 
+#### [Kubernetes](#tab/kubernetes)
+
+```yaml
+apiVersion: azconfig.io/v1
+kind: AzureAppConfigurationProvider
+metadata:
+  name: appconfigurationprovider-sample
+spec:
+  endpoint: <your-app-configuration-store-endpoint>
+  target:
+    configMapName: configmap-created-by-appconfig-provider
+  configuration:
+    selectors:
+      - keyFilter: TestApp*
+    refresh:
+      enabled: true
+      monitoring:
+        keyValues:
+          - key: SentinelKey
+```
+
 ---
 
 Both approaches are available through App Configuration providers across supported languages and platforms.

articles/azure-app-configuration/reference-kubernetes-provider.md

@@ -383,9 +383,7 @@ spec:
 
 ### Configuration refresh
 
-When you make changes to your data in Azure App Configuration, you might want those changes to be refreshed automatically in your Kubernetes cluster. It's common to update multiple key-values, but you don't want the cluster to pick up a change midway through the update. To maintain configuration consistency, you can use a key-value to signal the completion of your update. This key-value is known as the sentinel key. The Kubernetes provider can monitor this key-value, and the ConfigMap and Secret will only be regenerated with updated data once a change is detected in the sentinel key.
-
-In the following sample, a key-value named `app1_sentinel` is polled every minute, and the configuration is refreshed whenever changes are detected in the sentinel key.
+When you make changes to your data in Azure App Configuration, you might want those changes to be refreshed automatically in your Kubernetes cluster. In the following sample, the Kubernetes provider checks Azure App Configuration for updates every minute. The associated ConfigMap and Secret are regenerated only when changes are detected. For more information about monitoring configuration changes, see [Best practices for configuration refresh](./howto-best-practices.md#configuration-refresh).
 
 ``` yaml
 apiVersion: azconfig.io/v1
@@ -403,10 +401,6 @@ spec:
     refresh:
       enabled: true
       interval: 1m
-      monitoring:
-        keyValues:
-          - key: app1_sentinel
-            label: common
 ```
 
 ### Key Vault references