From ebec62479e4a6f1a9c62cbb32675402f618f1b37 Mon Sep 17 00:00:00 2001 From: natemollica-dev <57850649+natemollica-nm@users.noreply.github.com> Date: Thu, 16 Jan 2025 14:44:41 -0800 Subject: [PATCH] Update website/content/docs/k8s/deployment-configurations/datadog.mdx Co-authored-by: Jeff Boruszak <104028618+boruszak@users.noreply.github.com> --- .../content/docs/k8s/deployment-configurations/datadog.mdx | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/website/content/docs/k8s/deployment-configurations/datadog.mdx b/website/content/docs/k8s/deployment-configurations/datadog.mdx index 80bc0ed76a..ce580eb754 100644 --- a/website/content/docs/k8s/deployment-configurations/datadog.mdx +++ b/website/content/docs/k8s/deployment-configurations/datadog.mdx @@ -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. - 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 tls.crt, tls.key, and ca.crt secret volumes at the /etc/datadog-agent/conf.d/consul.d/certs - path within the Datadog Agent pod's agent 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. ### Helm Chart Configuration