Fixes #254 by removing the escape codes completely, as there isn't a native way to detect support during templating. It was fun while it lasted, but ultimately not great for Windows users.
Below is the NOTES output from an example install.
NOTES:
--------------------------------------------------------------------------------
__ __ __
\ \ / / / /
\ V / / /
\_/ \/
V E C T O R
--------------------------------------------------------------------------------
Vector is starting in your cluster. After a few minutes, you can use Vector's
API to view internal metrics by running:
$ kubectl -n default exec -it statefulset/vector -- vector top
--------------------------------------------------------------------------------
datadog_agent:
To forward logs from Datadog Agents deployed with the "datadog" Helm chart,
include the following in the "values.yaml" for your "datadog" chart:
For Datadog Agents version "7.34"/"6.34" or lower:
datadog:
containerExclude: "name:vector"
logs:
enabled: true
containerCollectAll: true
agents:
useConfigMap: true
customAgentConfig:
kubelet_tls_verify: false
logs_config:
logs_dd_url: "vector.default:8282"
logs_no_ssl: true
use_http: true
For Datadog Agents version "7.35"/"6.35" or greater:
datadog:
containerExclude: "name:vector"
logs:
enabled: true
containerCollectAll: true
agents:
useConfigMap: true
customAgentConfig:
kubelet_tls_verify: false
vector:
logs:
enabled: true
url: "http://vector.default:8282"
metrics:
enabled: true
url: "http://vector.default:8282"
Signed-off-by: Spencer Gilbert spencer.gilbert@datadoghq.com
Fixes #254 by removing the escape codes completely, as there isn't a native way to detect support during templating. It was fun while it lasted, but ultimately not great for Windows users.
Below is the NOTES output from an example install.