From 4aa4a8937359b9ab90fe7dba4c38d4bf87d69daf Mon Sep 17 00:00:00 2001 From: natemollica-dev <57850649+natemollica-nm@users.noreply.github.com> Date: Wed, 15 Jan 2025 16:09:12 -0800 Subject: [PATCH] Update datadog.mdx Reword the end user note to be in an English-understandable format. --- .../content/docs/k8s/deployment-configurations/datadog.mdx | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/website/content/docs/k8s/deployment-configurations/datadog.mdx b/website/content/docs/k8s/deployment-configurations/datadog.mdx index c3df799f4df4..80bc0ed76a7f 100644 --- a/website/content/docs/k8s/deployment-configurations/datadog.mdx +++ b/website/content/docs/k8s/deployment-configurations/datadog.mdx @@ -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. - 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 tls.crt, tls.key, - and ca.crt secret volumes at the /etc/datadog-agent/conf.d/consul.d/certs 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 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. ### Helm Chart Configuration