Skip to content

Commit f1fe950

Browse files
committed
modify heading
1 parent fa9057a commit f1fe950

File tree

3 files changed

+2
-2
lines changed

3 files changed

+2
-2
lines changed

articles/azure-app-configuration/integrate-kubernetes-deployment-helm.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.author: shuawan
1212

1313
#Customer intent: I want to use Azure App Configuration data in Kubernetes deployment with Helm.
1414
---
15-
# Integrate with Kubernetes Deployment Using Helm
15+
# Integrate with Kubernetes Deployment using Helm
1616

1717
Helm provides a way to define, install, and upgrade applications running in Kubernetes. A Helm chart contains the information necessary to create an instance of a Kubernetes application. Configuration is stored outside of the chart itself, in a file called *values.yaml*.
1818

@@ -179,7 +179,7 @@ settings:
179179
message: myMessage
180180
```
181181

182-
## Pass configuration data from App Configuration during Helm install ##
182+
## Pass configuration from App Configuration during Helm install ##
183183
First, download the configuration from App Configuration to a *myConfig.yaml* file. Use a key filter to only download those keys that start with **settings.**. If in your case the key filter is not sufficient to exclude keys of Key Vault references, you may use the argument **--skip-keyvault** to exclude them.
184184

185185
> [!TIP]

0 commit comments

Comments
 (0)