Skip to content

Commit

Permalink
edits
Browse files Browse the repository at this point in the history
  • Loading branch information
celenechang committed Jun 18, 2024
1 parent 207a01d commit e079e30
Showing 1 changed file with 17 additions and 5 deletions.
22 changes: 17 additions & 5 deletions docs/remote_config.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,12 +14,24 @@ You can create a policy on the Fleet Automation page to enable a feature for an

## Enabling Remote Configuration

Remote Configuration is disabled by default. To enable it using the [datadog-operator Helm chart](https://github.com/DataDog/helm-charts/tree/main/charts/datadog-operator), in your `values.yaml` file make the following changes:
Remote Configuration is disabled by default. To enable it using the latest [datadog-operator Helm chart](https://github.com/DataDog/helm-charts/tree/main/charts/datadog-operator), create a Kubernetes Secret that contains your API and application keys:

1. Set `remoteConfiguration.enabled=true`.
2. Set a cluster name, `clusterName`.
3. Set Datadog credentials, using `apiKey/apiKeyExistingSecret` and `appKey/appKeyExistingSecret`. (If using a secret, create the secret with
`kubectl create secret generic datadog-secret --from-literal api-key=<DATADOG_API_KEY> --from-literal app-key=<DATADOG_APP_KEY>`.)
```shell
export DD_API_KEY=<YOUR_API_KEY>
export DD_APP_KEY=<YOUR_APP_KEY>

kubectl create secret generic datadog-operator-secret --from-literal api-key=$DD_API_KEY --from-literal app-key=$DD_APP_KEY
```

Then modify your `values.yaml` file with the following:

```yaml
clusterName: example-cluster-name
remoteConfiguration:
enabled: true
apiKeyExistingSecret: datadog-operator-secret
appKeyExistingSecret: datadog-operator-secret
```
Then install the Datadog Operator:
Expand Down

0 comments on commit e079e30

Please sign in to comment.