-
Notifications
You must be signed in to change notification settings - Fork 16.8k
Better document cluster agent & Update chart #8786
Conversation
stable/datadog/values.yaml
Outdated
@@ -3,7 +3,7 @@ image: | |||
# This chart is compatible with different images, please choose one | |||
repository: datadog/agent # Agent6 | |||
# repository: datadog/dogstatsd # Standalone DogStatsD6 | |||
tag: 6.5.2 # Use 6.5.2-jmx to enable jmx fetch collection | |||
tag: 6.6.0 # Use 6.5.2-jmx to enable jmx fetch collection |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could you update the comment as well?
stable/datadog/OWNERS
Outdated
@@ -2,7 +2,9 @@ approvers: | |||
- hkaj | |||
- irabinovitch | |||
- xvello | |||
- charlyf |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes please! You'll need to open an issue to become a trusted collaborator first though.
e4965cf
to
30ddbc5
Compare
30ddbc5
to
a1f638b
Compare
Signed-off-by: charlyF <charly@datadoghq.com>
Signed-off-by: charlyF <charly@datadoghq.com>
Signed-off-by: charlyF <charly@datadoghq.com>
Signed-off-by: charlyF <charly@datadoghq.com>
a1f638b
to
2dc2d42
Compare
stable/datadog/README.md
Outdated
Read about the Datadog Cluster Agent in the [official documentation](https://docs.datadoghq.com/agent/kubernetes/cluster/). | ||
|
||
Run the following if you want to deploy the chart with the Datadog Cluster Agent. | ||
You can also specify `clusterAgent.metricsProvider.enabled=true` if you want to enable the External Metrics Server. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is already set in the command below. Either remove this line or remove the option in the bash snippet.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should keep both, just to stress that this is the specific option that enables the external metrics provider.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fair enough, then we should change the wording.
Right now it reads as Run the following [...], you can also specify <option> if you want to enable [...]
but the option is already in the snippet.
What about Note that specifying <option> will enable [...]
instead?
stable/datadog/README.md
Outdated
If you want to learn to use this feature, you can check out this [walkthrough](https://github.com/DataDog/datadog-agent/blob/master/docs/cluster-agent/CUSTOM_METRICS_SERVER.md). | ||
```bash | ||
helm install --name datadog-monitoring \ | ||
--set clusterAgent.token=YOUR-32-CHARACTERS-TOKEN \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
actually i think we should just get rid of this setting and generate a random token ourselves with {{ randAlphaNum 32 | quote }}
. WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
smart
stable/datadog/README.md
Outdated
--set clusterAgent.token=YOUR-32-CHARACTERS-TOKEN \ | ||
--set datadog.apiKey=YOUR-API-KEY-HERE \ | ||
--set datadog.appKey=YOUR-APP-KEY-HERE \ | ||
--set datadog.leaderElection=true \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we just turn leader election on for the cluster agent by default and get rid of this option? What could go wrong if we do? (of course we'd keep the option for when the cluster agent is not enabled).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agreed
Signed-off-by: charlyF <charly@datadoghq.com>
Signed-off-by: charlyF <charly@datadoghq.com>
Signed-off-by: charlyF <charly@datadoghq.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
values.yaml
has leaderElection: false
uncommented. That means the default value for the cluster agent won't apply and leaderElection won't be enabled by default. I think we should comment it out, and make it false by default for the agent but true for the cluster agent. Does that make sense?
stable/datadog/README.md
Outdated
Run the following if you want to deploy the chart with the Datadog Cluster Agent. | ||
Note that specifying `clusterAgent.metricsProvider.enabled=true` will enable the External Metrics Server. | ||
If you want to learn to use this feature, you can check out this [walkthrough](https://github.com/DataDog/datadog-agent/blob/master/docs/cluster-agent/CUSTOM_METRICS_SERVER.md). | ||
The Leader Election is enabled by default in the chart for the Cluster Agent. Only the Cluster Agent(s) participate in the election, in case you have several replicas configred (using `clusterAgent.replicas`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
configred
--> configured
stable/datadog/templates/NOTES.txt
Outdated
@@ -47,11 +47,12 @@ Create an application key at https://app.datadoghq.com/account/settings#api | |||
{{- if not .Values.clusterAgent.token }} | |||
|
|||
############################################################################## | |||
#### ERROR: You did not set a clusterAgent.token #### | |||
#### WARNING: You did not set a clusterAgent.token #### |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i'm fine with notifying it, but INFO
is enough IMHO? There's nothing wrong here.
- name: DD_LEADER_ELECTION | ||
value: {{ .Values.datadog.leaderElection | quote}} | ||
{{- end }} | ||
value: {{ .Values.datadog.leaderElection | default "true" | quote}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As an aside: could we rename this file to cluster-agent-deployment.yaml
? This confuses me every time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, I'll do it here
I'm ok with commenting it out in the docs to be more clear but from my testings and given that: |
Signed-off-by: charlyF <charly@datadoghq.com>
/approve |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CharlyF, hkaj The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* updating README Signed-off-by: charlyF <charly@datadoghq.com> * changing log level to warning Signed-off-by: charlyF <charly@datadoghq.com> * bumping chart, lint, updating agent version Signed-off-by: charlyF <charly@datadoghq.com> * updating versions in readme and comment Signed-off-by: charlyF <charly@datadoghq.com> * leader election is set to true by default Signed-off-by: charlyF <charly@datadoghq.com> * adding option and doc to generate and use random token if not provided Signed-off-by: charlyF <charly@datadoghq.com> * rephrase README Signed-off-by: charlyF <charly@datadoghq.com> * feedback Signed-off-by: charlyF <charly@datadoghq.com> * commenting leaderelection option in values.yaml Signed-off-by: charlyF <charly@datadoghq.com>
What this PR does / why we need it:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]