github
/
consul
mirror of https://github.com/hashicorp/consul
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update datadog.mdx 

Reword the end user note to be in an English-understandable format.
pull/22077/head
natemollica-dev 2025-01-15 16:09:12 -08:00 committed by GitHub
parent 88539f1b7e
commit 4aa4a89373
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
website/content/docs/k8s/deployment-configurations/datadog.mdx
View File

@ -293,9 +293,10 @@ during normal operation beyond that of Consul's available metrics.
See the below [table](#additional-integration-checks-performed) for an outline of the features added by the official integration.
<Note>
Currently, the annotations configured by the Helm overrides with Consul RPC TLS enabled
assume server and ca certificate secrets are shared with the Datadog agent release namespace and mount the valid <code>tls.crt</code>, <code>tls.key</code>,
and <code>ca.crt</code> secret volumes at the <code>/etc/datadog-agent/conf.d/consul.d/certs</code> path on the Datadog Agent, agent container.
Currently, the annotations configured by the Helm overrides, when Consul RPC TLS is enabled,
presume the user has shared the server and ca certificate secrets with the Datadog agent's Kubernetes namespace and
mount the valid <code>tls.crt</code>, <code>tls.key</code>, and <code>ca.crt</code> secret volumes at the <code>/etc/datadog-agent/conf.d/consul.d/certs</code>
path within the Datadog Agent pod's <code>agent</code> container.
</Note>
### Helm Chart Configuration