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

Update website/content/docs/k8s/deployment-configurations/datadog.mdx 

Co-authored-by: Jeff Boruszak <104028618+boruszak@users.noreply.github.com>
pull/22077/head
natemollica-dev 2025-01-16 14:44:41 -08:00 committed by GitHub
parent 4aa4a89373
commit ebec62479e
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -293,10 +293,7 @@ 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, 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.
When Consul RPC TLS is enabled, the annotations configured by the Helm overrides assume that the user already shared the server and CA certificate secrets with the Datadog agent's Kubernetes namespace. As a result, it mounts `tls.crt`, `tls.key`, and `ca.crt` secret volumes at the `/etc/datadog-agent/conf.d/consul.d/certs` path in the `agent` container of the Datadog agent's Pod.
</Note>
### Helm Chart Configuration