Skip to content

Commit de73bde

Browse files
committed
rename sentinel key
1 parent 91c9163 commit de73bde

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -297,7 +297,7 @@ spec:
297297

298298
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.
299299

300-
In the following sample, a key-value named `sentinelKey` is polled every minute, and the configuration is refreshed whenever changes are detected in the sentinel key.
300+
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.
301301

302302
``` yaml
303303
apiVersion: azconfig.io/v1beta1
@@ -316,7 +316,7 @@ spec:
316316
interval: 1m
317317
monitoring:
318318
keyValues:
319-
- key: sentinelKey
319+
- key: app1_sentinel
320320
label: common
321321
```
322322

0 commit comments

Comments
 (0)