All yaml snippets below are expected to be propertly merged into the main values.yaml
.
Notes based on:
- EKS 1.21.2
- Helm Chart 2.20.1
- Agent 7.30.0
- Cluster Agent 1.14.0
PassS services like EKS do not give us access to control plane nodes. Since we cannot deploy agents to control plane nodes, we cannot leverage Autodiscovery to automatically detect and start monitoring control plane services. EKS exposes the Kubernetes API as a service we can monitor using cluster checks for simplicity.
clusterAgent:
confd:
kube_apiserver_metrics.yaml: |-
cluster_check: true
init_config:
instances:
- prometheus_url: https://kubernetes.default/metrics
ssl_ca_cert: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
bearer_token_auth: true
kube_controller_manager.yaml: |-
cluster_check: true
init_config:
instances:
- prometheus_url: https://kubernetes.default/metrics
ssl_ca_cert: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
bearer_token_auth: true
kubelet - kubelet.d/conf.yaml
If tlsVerify: false
is not acceptable, you can specify the host and CA for the kubelet.
datadog:
kubelet:
host:
valueFrom:
fieldRef:
fieldPath: spec.nodeName
hostCAPath: /etc/kubernetes/pki/ca.crt