mirror of
https://github.com/helm/charts.git
synced 2026-08-23 22:37:45 +00:00
[datadog] Update README (#9416)
* [datadog] Update README Signed-off-by: Pierre <mfpierre@gmail.com> * [datadog] bump chart version Signed-off-by: Pierre <mfpierre@gmail.com>
This commit is contained in:
committed by
k8s-ci-robot
parent
5f9580805d
commit
cd01e234e8
@@ -1,5 +1,5 @@
|
||||
name: datadog
|
||||
version: 1.10.2
|
||||
version: 1.10.3
|
||||
appVersion: 6.6.0
|
||||
description: DataDog Agent
|
||||
keywords:
|
||||
|
||||
@@ -15,15 +15,15 @@ Kubernetes 1.4+ or OpenShift 3.4+ (1.3 support is currently partial, full suppor
|
||||
To install the chart with the release name `my-release`, retrieve your Datadog API key from your [Agent Installation Instructions](https://app.datadoghq.com/account/settings#agent/kubernetes) and run:
|
||||
|
||||
```bash
|
||||
$ helm install --name my-release \
|
||||
--set datadog.apiKey=YOUR-KEY-HERE stable/datadog
|
||||
helm install --name my-release \
|
||||
--set datadog.apiKey=YOUR-KEY-HERE stable/datadog
|
||||
```
|
||||
|
||||
After a few minutes, you should see hosts and metrics being reported in Datadog.
|
||||
|
||||
**Tip**: List all releases using `helm list`
|
||||
|
||||
### Enabling the Datadog Cluster Agent ###
|
||||
### Enabling the Datadog Cluster Agent
|
||||
|
||||
Read about the Datadog Cluster Agent in the [official documentation](https://docs.datadoghq.com/agent/kubernetes/cluster/).
|
||||
|
||||
@@ -47,7 +47,7 @@ helm install --name datadog-monitoring \
|
||||
To uninstall/delete the `my-release` deployment:
|
||||
|
||||
```bash
|
||||
$ helm delete my-release
|
||||
helm delete my-release
|
||||
```
|
||||
|
||||
The command removes all the Kubernetes components associated with the chart and deletes the release.
|
||||
@@ -120,15 +120,15 @@ The following table lists the configurable parameters of the Datadog chart and t
|
||||
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
|
||||
|
||||
```bash
|
||||
$ helm install --name my-release \
|
||||
--set datadog.apiKey=YOUR-KEY-HERE,datadog.logLevel=DEBUG \
|
||||
stable/datadog
|
||||
helm install --name my-release \
|
||||
--set datadog.apiKey=YOUR-KEY-HERE,datadog.logLevel=DEBUG \
|
||||
stable/datadog
|
||||
```
|
||||
|
||||
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
|
||||
|
||||
```bash
|
||||
$ helm install --name my-release -f my-values.yaml stable/datadog
|
||||
helm install --name my-release -f my-values.yaml stable/datadog
|
||||
```
|
||||
|
||||
**Tip**: You can copy and customize the default [values.yaml](values.yaml)
|
||||
@@ -213,6 +213,6 @@ podLabelsAsTags:
|
||||
As of the version 6.6.0, the Datadog Agent supports collecting metrics from any container runtime interface used in your cluster.
|
||||
Configure the location path of the socket with `datadog.criSocketPath` and make sure you allow the socket to be mounted into the pod running the agent by setting `datadog.useCriSocketVolume` to `True`.
|
||||
Standard paths are:
|
||||
- Docker socket: `/var/run/docker.sock`
|
||||
|
||||
- Containerd socket: `/var/run/containerd/containerd.sock`
|
||||
- Cri-o socket: `/var/run/crio/crio.sock`
|
||||
|
||||
Reference in New Issue
Block a user