github/deprecated-helm-charts
1
0
Fork 0
mirror of https://github.com/helm/charts.git synced 2026-08-23 22:37:45 +00:00
Code Issues Packages Projects Releases Wiki Activity

[stable/datadog] Typo and grammar fixes in documentation (#22944)

Browse Source 
* grammar edits!

Signed-off-by: Lénaïc Huard <lenaic.huard@datadoghq.com>

* Typo in log config

Signed-off-by: Lénaïc Huard <lenaic.huard@datadoghq.com>

Co-authored-by: cswatt <cecilia.watt@datadoghq.com>
Co-authored-by: John Girvan <3327314+jrgirvan@users.noreply.github.com>
This commit is contained in:
Lénaïc Huard
2020-06-25 01:58:38 -07:00
committed by GitHub
co-authored by cswatt John Girvan
parent df411feb22
commit d1efe909ac
4 changed files with 11 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
stable/datadog/CHANGELOG.md
+5
View File
@@ -1,5 +1,10 @@
# Datadog changelog
## 2.3.17
* grammar edits to datadog helm docs!
* Typo in log config
## 2.3.16
* Add parameter `clusterChecksRunner.rbac.serviceAccountAnnotations` for specifying annotations for dedicated ServiceAccount for Cluster Checks runners.
stable/datadog/Chart.yaml
+1 -1
View File
@@ -1,6 +1,6 @@
apiVersion: v1
name: datadog
version: 2.3.16
version: 2.3.17
appVersion: "7"
description: Datadog Agent
keywords:
stable/datadog/README.md
+1 -1
View File
@@ -131,7 +131,7 @@ datadog:
# (...)
logs:
enabled: true
configContainerCollectAll: true
containerCollectAll: true
```
then upgrade your Datadog Helm chart:
stable/datadog/docs/Migration_1.x_to_2.x.md
+4 -4
View File
@@ -1,9 +1,9 @@
# Chart 1.x to 2.x migration guide
The `datadog` chart has been refactored to regroup the `values.yaml` parameters in a more logical way.
Migrating from chart v1 to chart v2 hence requires to restructure the `values.yaml` file.
Migrating from chart v1 to chart v2 hence requires that you restructure the `values.yaml` file.
For all the parameters in the existing `values.yaml` file that applied to chart v1, you’ll
find to which parameters they correspond to in v2 in the following table.
find the parameters to which they correspond to in v2 in the following table.
Parameters that are not listed in the table below haven’t been touched and are at the same
location in v1 and v2.
@@ -13,7 +13,7 @@ location in v1 and v2.
| `image.tag` | `agents.image.tag` and `clusterCheckRunner.image.tag` | |
| `image.pullPolicy` | `agents.image.pullPolicy` and `clusterCheckRunner.image.pullPolicy` | |
| `image.pullSecrets` | `agents.image.pullSecrets` and `clusterCheckRunner.image.pullSecrets` | |
| `datadog.name` | ∅ | The name of the container inside the agent and cluster-agent pod isn’t configurable anymore |
| `datadog.name` | ∅ | The name of the container inside the Agent and Cluster Agent pod isn’t configurable anymore |
| `datadog.useCriSocketVolume` | ∅ | If `datadog.criSocketPath` is defined, the socket will be mounted inside the container without needing to set `datadog.useCriSocketVolume` in addition. |
| `datadog.containerLogsPath` | ∅ | Not needed anymore because the chart automatically detects if the CRI is `docker` based on `criSocketPath` and mounts the path accordingly |
| `datadog.apmEnabled` | `datadog.apm.enabled` | |
@@ -31,7 +31,7 @@ location in v1 and v2.
| `systemProbe.seccompRoot` | `datadog.systemProbe.seccompRoot` | |
| `systemProbe.bpfDebug` | `datadog.systemProbe.bpfDebug` | |
| `systemProbe.apparmor` | `datadog.systemProbe.apparmor` | |
| `clusterAgent.containerName` | ∅ | The name of the container inside the cluster agent pod isn’t configurable anymore |
| `clusterAgent.containerName` | ∅ | The name of the container inside the Cluster Agent pod isn’t configurable anymore |
| `clusterAgent.clusterChecks.enabled` | `datadog.clusterChecks.enabled` | |
| `rbac.create` | `agents.rbac.create` and `clusterAgent.rbac.create` | |
| `rbac.serviceAccountName` | `agents.rbac.serviceAccountName` and `clusterAgent.rabc.serviceAccountName` | |