Skip to content

Commit 0c83c11

Browse files
committed
resolve comments
1 parent b80f21b commit 0c83c11

File tree

1 file changed

+10
-7
lines changed

1 file changed

+10
-7
lines changed

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

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

1313
# Azure App Configuration Kubernetes Provider reference
1414

15-
The following reference outlines the properties supported by the Azure App Configuration Kubernetes Provider.
15+
The following reference outlines the properties supported by the Azure App Configuration Kubernetes Provider `v1.2.0`, see [release notes](https://github.com/Azure/AppConfiguration/blob/main/releaseNotes/KubernetesProvider.md) for more information on the change.
1616

1717
## Properties
1818

@@ -157,15 +157,18 @@ The `spec.featureFlag.refresh` property has the following child properties.
157157

158158
## Installation
159159

160-
You can use helm to [install Azure App Configuration Kubernetes Provider](https://mcr.microsoft.com/product/azure-app-configuration/kubernetes-provider/about#usage). To override default [helm-values](https://github.com/Azure/AppConfiguration-KubernetesProvider/blob/main/deploy/parameter/helm-values.yaml), use the `--set` flag and pass configuration from the command line.
160+
Use the following `helm install` command to install the Azure App Configuration Kubernetes Provider. See [helm-values.yaml](https://github.com/Azure/AppConfiguration-KubernetesProvider/blob/main/deploy/parameter/helm-values.yaml) for the complete list of parameters and their default values. You can override the default values by passing the `--set` flag to the command.
161+
162+
```bash
163+
helm install azureappconfiguration.kubernetesprovider \
164+
oci://mcr.microsoft.com/azure-app-configuration/helmchart/kubernetes-provider \
165+
--namespace azappconfig-system \
166+
--create-namespace
167+
```
161168

162169
### Autoscaling
163170

164-
It's useful to enable `autoscaling` when you need to deploy multiple instances of the `AzureAppConfigurationProvider` resource in AKS cluster. Setting `autoscaling.enabled` to `true` , [HorizontalPodAutoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/) will be used for managing pod autoscaling of Kubernetes Provider. `autoscaling` is disabled by default.
165-
166-
### Node assignment
167-
168-
You can set `nodeSelector`, `affinity` or `tolerations` to run Kubernetes Provider pod on particular nodes. For example, setting `nodeSelector.KEY=VALUE` during installation, Kubernetes Provider will be scheduled to the node with the label `KEY=VALUE`.
171+
By default, autoscaling is disabled. However, if you have multiple `AzureAppConfigurationProvider` resources to produce multiple ConfigMaps/Secrets and may hit a performance bottleneck of single pod, you can enable horizontal pod autoscaling by setting `autoscaling.enabled` to `true`.
169172

170173
## Examples
171174

0 commit comments

Comments
 (0)