## Default values for Datadog Agent

## See Datadog helm documentation to learn more:

## https://docs.datadoghq.com/agent/kubernetes/helm/

## FOR AN EFFORTLESS UPGRADE PATH, DO NOT COPY THIS FILE AS YOUR OWN values.yaml.

## ONLY SET THE VALUES YOU WANT TO OVERRIDE IN YOUR values.yaml.

# global.apmRegistryAllowList -- Restrict which registries can be used for APM library injection.

## When non-empty, only libraries from the listed registries will be injected. Enforced by both the

## admission controller webhook and the CSI driver. An empty list allows all registries (default).

global:

apmRegistryAllowList: []

# - public.ecr.aws/datadog

# - gcr.io/datadoghq

# nameOverride -- Override name of app

nameOverride: # ""

# fullnameOverride -- Override the full qualified app name

fullnameOverride: # ""

# kubeVersionOverride -- Override Kubernetes version detection. Useful for GitOps tools like FluxCD that don't expose the real cluster version to Helm

kubeVersionOverride: # "1.28.0"

# targetSystem -- Target OS for this deployment (possible values: linux, windows)

targetSystem: "linux"

# commonLabels -- Labels to apply to all resources

commonLabels: {}

# team_name: dev

# registry -- Registry to use for all Agent images (default depends on datadog.site and registryMigrationMode values)

## Currently we offer Datadog Agent images on:

## Datadog - use registry.datadoghq.com

## GCR US - use gcr.io/datadoghq

## GCR Europe - use eu.gcr.io/datadoghq

## GCR Asia - use asia.gcr.io/datadoghq

## Azure - use datadoghq.azurecr.io

## AWS - use public.ecr.aws/datadog

## DockerHub - use docker.io/datadog

## If you are on GKE Autopilot, you must use a gcr.io variant registry.

registry: # gcr.io/datadoghq

# registryMigrationMode -- Controls gradual migration of default image registry to

# registry.datadoghq.com, replacing site-specific regional mirrors (GCR, ACR).

# This setting has no effect when `registry` is explicitly set.

# GKE Autopilot and GKE GDC clusters are excluded and always use their site-specific gcr.io variant.

# US1-FED (ddog-gov.com) is excluded and always uses public.ecr.aws/datadog.

# US3 (us3.datadoghq.com) is excluded and always uses datadoghq.azurecr.io.

## "auto" (default): enable registry.datadoghq.com for sites where migration is rolled out.

## Currently enabled: AP1 (ap1.datadoghq.com), AP2 (ap2.datadoghq.com), US5 (us5.datadoghq.com), EU1 (datadoghq.eu), US1 (datadoghq.com, when APM is disabled).

## "all": enable registry.datadoghq.com for all sites (AP1, AP2, EU, US1, US5).

## "": disable migration, keeping site-specific registries.

registryMigrationMode: "auto"

datadog:

# datadog.apiKey -- Your Datadog API key

## ref: https://app.datadoghq.com/account/settings#agent/kubernetes

apiKey: # <DATADOG_API_KEY>

# datadog.apiKeyExistingSecret -- Use existing Secret which stores API key instead of creating a new one. The value should be set with the `api-key` key inside the secret.

## If set, this parameter takes precedence over "apiKey".

apiKeyExistingSecret: # <DATADOG_API_KEY_SECRET>

# datadog.appKey -- Datadog APP key required to use metricsProvider

## If you are using clusterAgent.metricsProvider.enabled = true, you must set

## a Datadog application key for read access to your metrics.

appKey: # <DATADOG_APP_KEY>

# datadog.appKeyExistingSecret -- Use existing Secret which stores APP key instead of creating a new one. The value should be set with the `app-key` key inside the secret.

## If set, this parameter takes precedence over "appKey".

appKeyExistingSecret: # <DATADOG_APP_KEY_SECRET>

# agents.secretAnnotations -- Annotations to add to the Secrets

secretAnnotations: {}

# key: "value"

## Configure the secret backend feature https://docs.datadoghq.com/agent/guide/secrets-management

## Examples: https://docs.datadoghq.com/agent/guide/secrets-management/#setup-examples-1

secretBackend:

# datadog.secretBackend.command -- Configure the secret backend command, path to the secret backend binary.

## Note: If the command value is "/readsecret_multiple_providers.sh", and datadog.secretBackend.enableGlobalPermissions is enabled below, the agents will have permissions to get secret objects across the cluster.

## Read more about "/readsecret_multiple_providers.sh": https://docs.datadoghq.com/agent/guide/secrets-management/#script-for-reading-from-multiple-secret-providers-readsecret_multiple_providerssh

command: # "/readsecret.sh" or "/readsecret_multiple_providers.sh" or any custom binary path

# datadog.secretBackend.arguments -- Configure the secret backend command arguments (space-separated strings).

arguments: # "/etc/secret-volume" or any other custom arguments

# datadog.secretBackend.timeout -- Configure the secret backend command timeout in seconds.

timeout: # 30

# datadog.secretBackend.refreshInterval -- [PREVIEW] Configure the secret backend command refresh interval in seconds.

refreshInterval: # 0

# datadog.secretBackend.type -- Configure the built-in secret backend type.

# Alternative to command; when set, the Agent uses the built-in backend to resolve secrets. Requires Agent 7.70+.

type: # Examples: "file.text", "k8s.secrets", "docker.secrets", "aws.secrets", etc.

# datadog.secretBackend.config -- Additional configuration for the secret backend type.

config: {}

# Example for k8s.secrets:

# token_path: "/custom/path/token"

# ca_path: "/custom/path/ca.crt"

# datadog.secretBackend.enableGlobalPermissions -- Whether to create a global permission allowing Datadog agents to read all secrets when `datadog.secretBackend.command` is set to `"/readsecret_multiple_providers.sh"` or `datadog.secretBackend.type` is set.

enableGlobalPermissions: true

# datadog.secretBackend.roles -- Creates roles for Datadog to read the specified secrets - replacing `datadog.secretBackend.enableGlobalPermissions`.

roles: []

# - namespace: secret-location-namespace

# secrets:

# - secret-1

# - secret-2

# datadog.securityContext -- Allows you to overwrite the default PodSecurityContext on the Daemonset or Deployment

securityContext:

runAsUser: 0

# seLinuxOptions:

# user: "system_u"

# role: "system_r"

# type: "spc_t"

# level: "s0"

# datadog.hostVolumeMountPropagation -- Allow to specify the `mountPropagation` value on all volumeMounts using HostPath

## ref: https://kubernetes.io/docs/concepts/storage/volumes/#mount-propagation

hostVolumeMountPropagation: None

# datadog.clusterName -- Set a unique cluster name to allow scoping hosts and Cluster Checks easily

## The name must be unique and must be dot-separated tokens with the following restrictions:

## * Lowercase letters, numbers, and hyphens only.

## * Must start with a letter.

## * Must end with a number or a letter.

## * Overall length should not be higher than 80 characters.

## Compared to the rules of GKE, dots are allowed whereas they are not allowed on GKE:

## https://cloud.google.com/kubernetes-engine/docs/reference/rest/v1beta1/projects.locations.clusters#Cluster.FIELDS.name

clusterName: # <CLUSTER_NAME>

# datadog.site -- The site of the Datadog intake to send Agent data to.

# (documentation: https://docs.datadoghq.com/getting_started/site/)

## Set to 'datadoghq.com' to send data to the US1 site (default).

## Set to 'datadoghq.eu' to send data to the EU site.

## Set to 'us3.datadoghq.com' to send data to the US3 site.

## Set to 'us5.datadoghq.com' to send data to the US5 site.

## Set to 'ddog-gov.com' to send data to the US1-FED site.

## Set to 'ap1.datadoghq.com' to send data to the AP1 site.

site: # datadoghq.com

# datadog.dd_url -- The host of the Datadog intake server to send Agent data to, only set this option if you need the Agent to send data to a custom URL

## Overrides the site setting defined in "site".

dd_url: # https://app.datadoghq.com

# datadog.logLevel -- Set logging verbosity, valid log levels are: trace, debug, info, warn, error, critical, off

logLevel: INFO

# datadog.kubeStateMetricsEnabled -- If true, deploys the kube-state-metrics deployment

## ref: https://github.com/kubernetes/kube-state-metrics/tree/kube-state-metrics-helm-chart-2.13.2/charts/kube-state-metrics

# The kubeStateMetricsEnabled option will be removed in the 4.0 version of the Datadog Agent chart.

kubeStateMetricsEnabled: false

kubeStateMetricsNetworkPolicy:

# datadog.kubeStateMetricsNetworkPolicy.create -- If true, create a NetworkPolicy for kube state metrics

create: false

kubeStateMetricsCore:

# datadog.kubeStateMetricsCore.enabled -- Enable the kubernetes_state_core check in the Cluster Agent (Requires Cluster Agent 1.12.0+)

## ref: https://docs.datadoghq.com/integrations/kubernetes_state_core

enabled: true

rbac:

# datadog.kubeStateMetricsCore.rbac.create -- If true, create & use RBAC resources

create: true

## Configuring this field changes the default kubernetes_state_core check configuration. Recommended for large clusters to reduce load on the API server.

useApiServerCache: false

# datadog.kubeStateMetricsCore.ignoreLegacyKSMCheck -- Disable the auto-configuration of legacy kubernetes_state check (taken into account only when datadog.kubeStateMetricsCore.enabled is true)

## Disabling this field is not recommended as it results in enabling both checks, it can be useful though during the migration phase.

## Migration guide: https://docs.datadoghq.com/integrations/kubernetes_state_core/?tab=helm#migration-from-kubernetes_state-to-kubernetes_state_core

ignoreLegacyKSMCheck: true

# datadog.kubeStateMetricsCore.collectSecretMetrics -- Enable watching secret objects and collecting their corresponding metrics kubernetes_state.secret.*

## Configuring this field will change the default kubernetes_state_core check configuration and the RBACs granted to Datadog Cluster Agent to run the kubernetes_state_core check.

collectSecretMetrics: true

# datadog.kubeStateMetricsCore.collectConfigMaps -- Enable watching configmap objects and collecting their corresponding metrics kubernetes_state.configmap.*

## Configuring this field will change the default kubernetes_state_core check configuration and the RBACs granted to Datadog Cluster Agent to run the kubernetes_state_core check.

collectConfigMaps: true

# datadog.kubeStateMetricsCore.collectVpaMetrics -- Enable watching VPA objects and collecting their corresponding metrics kubernetes_state.vpa.*

## Configuring this field will change the default kubernetes_state_core check configuration and the RBACs granted to Datadog Cluster Agent to run the kubernetes_state_core check.

collectVpaMetrics: false

# datadog.kubeStateMetricsCore.collectCrdMetrics -- Enable watching CRD objects and collecting their corresponding metrics kubernetes_state.crd.*

## Configuring this field will change the default kubernetes_state_core check configuration to run the kubernetes_state_core check.

collectCrdMetrics: false

# datadog.kubeStateMetricsCore.collectCrMetrics -- Enable watching CustomResource objects and collecting their corresponding metrics kubernetes_state_customresource.* (Requires Cluster Agent 7.63.0+)

## Configuring this field will change the default kubernetes_state_core check configuration and the RBACs granted to Datadog Cluster Agent to run the kubernetes_state_core check.

##

## See https://github.com/kubernetes/kube-state-metrics/blob/main/docs/metrics/extend/customresourcestate-metrics.md for a full description of each field.

collectCrMetrics: []

# - groupVersionKind:

# group: myteam.io

# kind: "Foo"

# version: "v1"

# resource: "foos" # optional, if not set, the resource will be pluralized from the kind by adding "s" to the end

# metrics:

# - name: "uptime"

# help: "Foo uptime"

# each:

# type: Gauge

# gauge:

# path: [status, uptime]

# datadog.kubeStateMetricsCore.collectApiServicesMetrics -- Enable watching apiservices objects and collecting their corresponding metrics kubernetes_state.apiservice.* (Requires Cluster Agent 7.45.0+)

## Configuring this field will change the default kubernetes_state_core check configuration and the RBACs granted to Datadog Cluster Agent to run the kubernetes_state_core check.

collectApiServicesMetrics: false

# datadog.kubeStateMetricsCore.useClusterCheckRunners -- For large clusters where the Kubernetes State Metrics Check Core needs to be distributed on dedicated workers.

## Configuring this field will create a separate deployment which will run Cluster Checks, including Kubernetes State Metrics Core.

## If clusterChecksRunner.enabled is true, it's recommended to set this flag to true as well to better utilize dedicated workers and reduce load on the Cluster Agent.

## ref: https://docs.datadoghq.com/agent/cluster_agent/clusterchecksrunner?tab=helm

useClusterCheckRunners: false

# datadog.kubeStateMetricsCore.labelsAsTags -- Extra labels to collect from resources and to turn into datadog tag.

## It has the following structure:

## labelsAsTags:

## <resource1>: # can be pod, deployment, node, etc.

## <label1>: <tag1> # where <label1> is the kubernetes label and <tag1> is the datadog tag

## <label2>: <tag2>

## <resource2>:

## <label3>: <tag3>

##

labelsAsTags: {}

# pod:

# app: app

# node:

# zone: zone

# team: team

# datadog.kubeStateMetricsCore.annotationsAsTags -- Extra annotations to collect from resources and to turn into datadog tag.

## It has the following structure:

## annotationsAsTags:

## <resource1>: # can be pod, deployment, node, etc.

## <annotation1>: <tag1> # where <annotation1> is the kubernetes annotation and <tag1> is the datadog tag

## <annotation2>: <tag2>

## <resource2>:

## <annotation3>: <tag3>

##

## Warning: the annotation must match the transformation done by kube-state-metrics,

## for example tags.datadoghq.com/version becomes tags_datadoghq_com_version.

annotationsAsTags: {}

# pod:

# app: app

# node:

# zone: zone

# team: team

# datadog.kubeStateMetricsCore.tags -- List of static tags to attach to all KSM metrics

tags: []

# datadog.kubeStateMetricsCore.namespaces -- Restrict the kubernetes_state_core check to collect metrics only from the specified namespaces.

## When set, namespace-scoped RBAC is created as Role+RoleBinding per listed namespace instead of a cluster-wide ClusterRole.

## Cluster-scoped resources (nodes, persistentvolumes, storageclasses, etc.) are still collected via a ClusterRole.

namespaces: []

# - default

# - kube-system

## Manage Cluster checks feature

## ref: https://docs.datadoghq.com/agent/autodiscovery/clusterchecks/

## Autodiscovery via Kube Service annotations is automatically enabled

clusterChecks:

# datadog.clusterChecks.enabled -- Enable the Cluster Checks feature on both the cluster-agents and the daemonset

enabled: true

# datadog.clusterChecks.shareProcessNamespace -- Set the process namespace sharing on the cluster checks agent

shareProcessNamespace: false

# datadog.nodeLabelsAsTags -- Provide a mapping of Kubernetes Node Labels to Datadog Tags

nodeLabelsAsTags: {}

# beta.kubernetes.io/instance-type: aws-instance-type

# kubernetes.io/role: kube_role

# <KUBERNETES_NODE_LABEL>: <DATADOG_TAG_KEY>

# datadog.podLabelsAsTags -- Provide a mapping of Kubernetes Labels to Datadog Tags

podLabelsAsTags: {}

# app: kube_app

# release: helm_release

# <KUBERNETES_LABEL>: <DATADOG_TAG_KEY>

# datadog.podAnnotationsAsTags -- Provide a mapping of Kubernetes Annotations to Datadog Tags

podAnnotationsAsTags: {}

# iam.amazonaws.com/role: kube_iamrole

# <KUBERNETES_ANNOTATIONS>: <DATADOG_TAG_KEY>

# datadog.namespaceLabelsAsTags -- Provide a mapping of Kubernetes Namespace Labels to Datadog Tags

namespaceLabelsAsTags: {}

# env: environment

# <KUBERNETES_NAMESPACE_LABEL>: <DATADOG_TAG_KEY>

# datadog.namespaceAnnotationsAsTags -- Provide a mapping of Kubernetes Namespace Annotations to Datadog Tags

namespaceAnnotationsAsTags: {}

# env: environment

# <KUBERNETES_NAMESPACE_ANNOTATIONS>: <DATADOG_TAG_KEY>

# datadog.kubernetesResourcesLabelsAsTags -- Provide a mapping of Kubernetes Resources Labels to Datadog Tags

kubernetesResourcesLabelsAsTags: {}

# pods:

# x-ref: reference

# namespaces:

# kubernetes.io/metadata.name: name-as-tag

# <RESOURCE_TYPE>:

# <KUBERNETES_RESOURCE_LABEL>: <DATADOG_TAG_KEY>

# datadog.kubernetesResourcesAnnotationsAsTags -- Provide a mapping of Kubernetes Resources Annotations to Datadog Tags

kubernetesResourcesAnnotationsAsTags: {}

# pods:

# x-ann: annotation-reference

# namespaces:

# stale-annotation: annotation-as-tag

# <RESOURCE_TYPE>:

# <KUBERNETES_RESOURCE_ANNOTATION>: <DATADOG_TAG_KEY>

originDetectionUnified:

# datadog.originDetectionUnified.enabled -- Enabled enables unified mechanism for origin detection. Default: false. (Requires Agent 7.54.0+).

enabled: false

# datadog.tags -- List of static tags to attach to every metric, event and service check collected by this Agent.

## Learn more about tagging: https://docs.datadoghq.com/tagging/

tags: []

# - "<KEY_1>:<VALUE_1>"

# - "<KEY_2>:<VALUE_2>"

# datadog.checksCardinality -- Sets the tag cardinality for the checks run by the Agent.

## ref: https://docs.datadoghq.com/getting_started/tagging/assigning_tags/?tab=containerizedenvironments#environment-variables

checksCardinality: # low, orchestrator or high (not set by default to avoid overriding existing DD_CHECKS_TAG_CARDINALITY configurations, the default value in the Agent is low)

# kubelet configuration

kubelet:

# datadog.kubelet.host -- Override kubelet IP

host:

valueFrom:

fieldRef:

fieldPath: status.hostIP

# datadog.kubelet.tlsVerify -- Toggle kubelet TLS verification

# @default -- true

tlsVerify: # false

# datadog.kubelet.hostCAPath -- Path (on host) where the Kubelet CA certificate is stored

# @default -- None (no mount from host)

hostCAPath:

# datadog.kubelet.agentCAPath -- Path (inside Agent containers) where the Kubelet CA certificate is stored

# @default -- /var/run/host-kubelet-ca.crt if hostCAPath else /var/run/secrets/kubernetes.io/serviceaccount/ca.crt

agentCAPath:

# datadog.kubelet.podLogsPath -- Path (on host) where the PODs logs are located

# @default -- /var/log/pods on Linux, C:\var\log\pods on Windows

podLogsPath:

# datadog.kubelet.coreCheckEnabled -- Toggle if kubelet core check should be used instead of Python check. (Requires Agent/Cluster Agent 7.53.0+)

# @default -- true

coreCheckEnabled: true

# datadog.kubelet.podResourcesSocketDir -- Path (on host) where the kubelet.sock socket for the PodResources API is located

# @default -- /var/lib/kubelet/pod-resources

podResourcesSocketDir: /var/lib/kubelet/pod-resources

# datadog.kubelet.useApiServer -- Enable this to query the pod list from the API Server instead of the Kubelet. (Requires Agent 7.65.0+)

# @default -- false

useApiServer: false

# datadog.kubelet.fineGrainedAuthorization -- Enable fine-grained authentication for kubelet (requires: Kubernetes 1.32+)

fineGrainedAuthorization: false

# datadog.expvarPort -- Specify the port to expose pprof and expvar to not interfere with the agent metrics port from the cluster-agent, which defaults to 5000

expvarPort: 6000

## dogstatsd configuration

## ref: https://docs.datadoghq.com/agent/kubernetes/dogstatsd/

## To emit custom metrics from your Kubernetes application, use DogStatsD.

dogstatsd:

# datadog.dogstatsd.port -- Override the Agent DogStatsD port

## Note: Make sure your client is sending to the same UDP port.

port: 8125

# datadog.dogstatsd.originDetection -- Enable origin detection for container tagging

## ref: https://docs.datadoghq.com/developers/dogstatsd/unix_socket/#using-origin-detection-for-container-tagging

originDetection: false

# datadog.dogstatsd.tags -- List of static tags to attach to every custom metric, event and service check collected by Dogstatsd.

## Learn more about tagging: https://docs.datadoghq.com/tagging/

tags: []

# - "<KEY_1>:<VALUE_1>"

# - "<KEY_2>:<VALUE_2>"

# datadog.dogstatsd.tagCardinality -- Sets the tag cardinality relative to the origin detection

## ref: https://docs.datadoghq.com/developers/dogstatsd/unix_socket/#using-origin-detection-for-container-tagging

tagCardinality: low

# datadog.dogstatsd.useSocketVolume -- Enable dogstatsd over Unix Domain Socket with an HostVolume

## ref: https://docs.datadoghq.com/developers/dogstatsd/unix_socket/

useSocketVolume: true

# datadog.dogstatsd.socketPath -- Path to the DogStatsD socket

socketPath: /var/run/datadog/dsd.socket

# datadog.dogstatsd.hostSocketPath -- Host path to the DogStatsD socket

hostSocketPath: /var/run/datadog

# datadog.dogstatsd.useHostPort -- Sets the hostPort to the same value of the container port

## Needs to be used for sending custom metrics.

## The ports need to be available on all hosts.

##

## WARNING: Make sure that hosts using this are properly firewalled otherwise

## metrics and traces are accepted from any host able to connect to this host.

useHostPort: false

# datadog.dogstatsd.useHostPID -- Run the agent in the host's PID namespace

## DEPRECATED: use datadog.useHostPID instead.

## This is required for Dogstatsd origin detection to work.

## See https://docs.datadoghq.com/developers/dogstatsd/unix_socket/

useHostPID: false

# datadog.dogstatsd.nonLocalTraffic -- Enable this to make each node accept non-local statsd traffic (from outside of the pod)

## ref: https://github.com/DataDog/docker-dd-agent#environment-variables

nonLocalTraffic: true

# datadog.useHostPID -- Run the agent in the host's PID namespace, required for origin detection

# / unified service tagging

## This is required for Dogstatsd origin detection to work in dogstatsd and trace agent

## See https://docs.datadoghq.com/developers/dogstatsd/unix_socket/

useHostPID: true

# datadog.collectEvents -- Enables this to start event collection from the kubernetes API

## ref: https://docs.datadoghq.com/agent/kubernetes/#event-collection

collectEvents: true

# datadog.kubernetesUseEndpointSlices -- Enable this to map Kubernetes services to endpointslices instead of endpoints. (Requires Cluster Agent 7.62.0+).

kubernetesUseEndpointSlices: true

# datadog.kubernetesKubeServiceIgnoreReadiness -- Enable this to attach kube_service tag unconditionally. (Requires Cluster Agent 7.76.0+).

kubernetesKubeServiceIgnoreReadiness: false

# Configure Kubernetes events collection

kubernetesEvents:

# datadog.kubernetesEvents.sourceDetectionEnabled -- Enable this to map Kubernetes events to integration sources based on controller names. (Requires Cluster Agent 7.56.0+).

sourceDetectionEnabled: false

# datadog.kubernetesEvents.filteringEnabled -- Enable this to only include events that match the pre-defined allowed events. (Requires Cluster Agent 7.57.0+).

filteringEnabled: false

# datadog.kubernetesEvents.unbundleEvents -- Allow unbundling kubernetes events, 1:1 mapping between Kubernetes and Datadog events. (Requires Cluster Agent 7.42.0+).

unbundleEvents: false

# datadog.kubernetesEvents.collectedEventTypes -- Event types to be collected. This requires datadog.kubernetesEvents.unbundleEvents to be set to true.

collectedEventTypes:

# - kind: <kubernetes resource kind> # (optional if `source`` is provided)

# source: <controller name> # (optional if `kind`` is provided)

# reasons: # (optional) if empty accept all event reasons

# - <kubernetes event reason>

- kind: Pod

reasons:

- Failed

- BackOff

- Unhealthy

- FailedScheduling

- FailedMount

- FailedAttachVolume

- kind: Node

reasons:

- TerminatingEvictedPod

- NodeNotReady

- Rebooted

- HostPortConflict

- kind: CronJob

reasons:

- SawCompletedJob

# datadog.kubernetesEvents.maxEventsPerRun -- Maximum number of events you wish to collect per check run.

maxEventsPerRun:

# datadog.kubernetesEvents.kubernetesEventResyncPeriodS -- Specify the frequency in seconds at which the Agent should list all events to re-sync following the informer pattern

kubernetesEventResyncPeriodS:

clusterTagger:

# datadog.clusterTagger.collectKubernetesTags -- Enables Kubernetes resources tags collection.

collectKubernetesTags: false

# datadog.leaderElection -- Enables leader election mechanism for event collection

leaderElection: true

# datadog.leaderLeaseDuration -- Set the lease time for leader election in second

leaderLeaseDuration: # 60

# datadog.leaderElectionResource -- Selects the default resource to use for leader election.

# Can be:

# * "lease" / "leases". Only supported in agent 7.47+

# * "configmap" / "configmaps".

# "" to automatically detect which one to use.

leaderElectionResource: configmap

remoteConfiguration:

# datadog.remoteConfiguration.enabled -- Set to true to enable remote configuration.

# DEPRECATED: Consider using remoteConfiguration.enabled instead

enabled: true

privateActionRunner:

# datadog.privateActionRunner.enabled -- Enable the Private Action Runner on the node agent to execute workflow actions

enabled: false

# datadog.privateActionRunner.selfEnroll -- Enable self-enrollment for the Private Action Runner

## When enabled, the runner will automatically register itself with Datadog using the provided API/APP keys

## and store its identity in a local file. Requires leader election to be enabled.

selfEnroll: true

# datadog.privateActionRunner.urn -- URN of the Private Action Runner (required if selfEnroll is false)

## Format: urn:datadog:private-action-runner:organization:<org_id>:runner:<runner_id>

urn: # "urn:datadog:private-action-runner:organization:123456:runner:abc-def"

# datadog.privateActionRunner.privateKey -- Private key for the Private Action Runner (required if selfEnroll is false)

## This key is used to authenticate the runner with Datadog

privateKey: # "<PRIVATE_KEY>"

# datadog.privateActionRunner.identityFromExistingSecret -- Use existing Secret which stores the Private Action Runner URN and private key

## The secret should contain 'urn' and 'private_key' keys

## If set, this parameter takes precedence over "urn" and "privateKey"

identityFromExistingSecret: # "<PAR_SECRET_NAME>"

# datadog.privateActionRunner.actionsAllowlist -- List of actions executable by the Private Action Runner

actionsAllowlist: []

# - "com.datadoghq.http.request"

# - "com.datadoghq.gitlab.branches.*"

## Enable logs agent and provide custom configs

logs:

# datadog.logs.enabled -- Enables this to activate Datadog Agent log collection

## ref: https://docs.datadoghq.com/agent/basic_agent_usage/kubernetes/#log-collection-setup

enabled: false

# datadog.logs.containerCollectAll -- Enable this to allow log collection for all containers

## ref: https://docs.datadoghq.com/agent/basic_agent_usage/kubernetes/#log-collection-setup

containerCollectAll: false

# datadog.logs.containerCollectUsingFiles -- Collect logs from files in /var/log/pods instead of using container runtime API

## It's usually the most efficient way of collecting logs.

## ref: https://docs.datadoghq.com/agent/basic_agent_usage/kubernetes/#log-collection-setup

containerCollectUsingFiles: true

# datadog.logs.autoMultiLineDetection -- Allows the Agent to detect common multi-line patterns automatically.

## ref: https://docs.datadoghq.com/agent/logs/advanced_log_collection/?tab=configurationfile#automatic-multi-line-aggregation

autoMultiLineDetection: false

## Enable apm agent and provide custom configs

##

## APM is enabled by default. If local service Internal Traffic Policy is allowed (Kubernetes v1.22+), the agent service is created with the APM local traceport.

apm:

# datadog.apm.socketEnabled -- Enable APM over Socket (Unix Socket or windows named pipe)

## ref: https://docs.datadoghq.com/agent/kubernetes/apm/

socketEnabled: true

# datadog.apm.portEnabled -- Enable APM over TCP communication (hostPort 8126 by default)

## ref: https://docs.datadoghq.com/agent/kubernetes/apm/

portEnabled: false

# datadog.apm.useLocalService -- Enable APM over TCP communication to use the local service only (requires Kubernetes v1.22+)

# Note: The hostPort 8126 is disabled when this is enabled.

## ref: https://docs.datadoghq.com/tracing/guide/setting_up_apm_with_kubernetes_service/?tab=helm

useLocalService: false

# datadog.apm.enabled -- Enable this to enable APM and tracing, on port 8126

# DEPRECATED. Use datadog.apm.portEnabled instead

## ref: https://github.com/DataDog/docker-dd-agent#tracing-from-the-host

enabled: false

# datadog.apm.port -- Override the trace Agent port

## Note: Make sure your client is sending to the same UDP port.

port: 8126

# datadog.apm.useSocketVolume -- Enable APM over Unix Domain Socket

# DEPRECATED. Use datadog.apm.socketEnabled instead

## ref: https://docs.datadoghq.com/agent/kubernetes/apm/

useSocketVolume: false

# datadog.apm.socketPath -- Path to the trace-agent socket

socketPath: /var/run/datadog/apm.socket

# datadog.apm.hostSocketPath -- Host path to the trace-agent socket

hostSocketPath: /var/run/datadog

# Error Tracking backend

errorTrackingStandalone:

# datadog.apm.errorTrackingStandalone.enabled -- Enables Error Tracking for backend services.

enabled: false

# APM Single Step Instrumentation

# Requires Cluster Agent 7.49+.

instrumentation:

# datadog.apm.instrumentation.enabled -- Enable injecting the Datadog APM libraries into all pods in the cluster.

enabled: false

# datadog.apm.instrumentation.enabledNamespaces -- Enable injecting the Datadog APM libraries into pods in specific namespaces.

enabledNamespaces: []

# datadog.apm.instrumentation.disabledNamespaces -- Disable injecting the Datadog APM libraries into pods in specific namespaces.

disabledNamespaces: []

# datadog.apm.instrumentation.libVersions -- Inject specific version of tracing libraries with Single Step Instrumentation.

libVersions: {}

# datadog.apm.instrumentation.targets -- Enable target based workload selection.

# Requires Cluster Agent 7.64.0+.

#

# ddTraceConfigs[]valueFrom Requires Cluster Agent 7.66.0+.

targets: []

# - name: "example"

# podSelector:

# matchLabels:

# language: "python"

# namespaceSelector:

# matchNames:

# - "applications"

# ddTraceVersions:

# python: "v2"

# ddTraceConfigs:

# - name: "DD_PROFILING_ENABLED"

# value: "true"

# - name: "DD_SERVICE"

# valueFrom:

# fieldRef:

# fieldPath: metadata.labels[my-label]

# datadog.apm.instrumentation.skipKPITelemetry -- Disable generating Configmap for APM Instrumentation KPIs

skipKPITelemetry: false

# Language detection currently only detects languages and adds them as annotations on deployments, but doesn't use these languages for injecting libraries to applicative pods.

# It requires Agent 7.52+ and Cluster Agent 7.52+

language_detection:

# datadog.apm.instrumentation.language_detection.enabled -- Run language detection to automatically detect languages of user workloads (preview).

enabled: true

# datadog.apm.instrumentation.injectionMode -- The injection mode to use for libraries injection.

# Valid values are: "auto", "init_container", "csi" (experimental, requires Cluster Agent 7.76.0+ and Datadog CSI Driver), "image_volume" (experimental, requires Cluster Agent 7.77.0+)

# Empty by default so the Cluster Agent can apply its own defaults.

injectionMode: ""

# This feature is in preview. It requires Cluster Agent 7.57+.

injector:

# datadog.apm.instrumentation.injector.imageTag -- The image tag to use for the APM Injector (preview).

imageTag: ""

## Application Security Managment (ASM) configuration

##

## ASM is disabled by default and can be enabled by setting the various `enabled` fields to `true` under the `datadog.asm` section.

## Manually adding the various environment variables to a pod will take precedence over the ones in the Helm chart.

## These will only have an effect on containers that have Datadog client libraries installed, either manually or via Single Step Instrumentation (under the `datadog.apm.instrumentation` section).

## It requires Datadog Cluster Agent 7.53.0+.

asm:

threats:

# datadog.asm.threats.enabled -- Enable Application Security Management Threats App & API Protection by injecting `DD_APPSEC_ENABLED=true` environment variable to all pods in the cluster

enabled: false

sca:

# datadog.asm.sca.enabled -- Enable Application Security Management Software Composition Analysis by injecting `DD_APPSEC_SCA_ENABLED=true` environment variable to all pods in the cluster

enabled: false

iast:

# datadog.asm.iast.enabled -- Enable Application Security Management Interactive Application Security Testing by injecting `DD_IAST_ENABLED=true` environment variable to all pods in the cluster

enabled: false

## App & API Protection configuration

##

## App & API Protection is disabled by default and can be enabled by setting the `enabled` field to `true` under the `datadog.appsec.injector` section.

## The Datadog Helm Chart offer the option to auto-instrument supported proxies in the cluster to forward traffic to a custom security processor delegating

## traffic analysis, WAF capabilities and API Posture management to Datadog's App and API Protection product that has to be deployed separately. Please follow the documentation to deploy the processor:

## https://docs.datadoghq.com/security/application_security/setup/#proxies

## It requires Datadog Cluster Agent 7.73.0+.

appsec:

# App & API Protection Injector is used to automatically configure your proxy to forward traffic to a custom security processor delegating

# traffic analysis, WAF capabilities and API Posture management to Datadog's App and API Protection product.

injector:

# datadog.appsec.injector.enabled -- Enable App & API Protection on your cluster ingress usage across all your cluster at once

enabled: false

# datadog.appsec.injector.autoDetect -- Automatically detect and inject supported proxies in the cluster (Envoy Gateway, Istio Gateway API, native Istio Gateway, ingress-nginx)

autoDetect: true

# datadog.appsec.injector.mode -- Deployment mode for the AppSec processor. Valid values: "sidecar", "external". Leave empty to use the agent default (sidecar). Upgrading users who rely on the external-processor flow (processor.address / processor.service.*) should set this to "external" explicitly.

mode: ""

# datadog.appsec.injector.proxies -- Manually specify which proxy types to inject. Valid values: "envoy-gateway", "istio", "istio-gateway", "ingress-nginx"

# When autoDetect is true, detected proxies are added to this list

# When autoDetect is false, only proxies in this list are enabled

proxies: []

# - envoy-gateway: Configures Envoy Gateway resources for AppSec injection

# - istio: Watches Istio-managed Kubernetes Gateway API GatewayClasses for AppSec injection

# - istio-gateway: Watches native Istio Gateway resources for AppSec injection

# - ingress-nginx: Watches IngressClass resources to discover ingress-nginx controllers and injects the nginx-datadog module via an init container

sidecar:

# datadog.appsec.injector.sidecar.image -- Container image for the AppSec sidecar processor

image: "ghcr.io/datadog/dd-trace-go/service-extensions-callout"

# datadog.appsec.injector.sidecar.imageTag -- Image tag for the AppSec sidecar processor

imageTag: "v2.8.2"

# datadog.appsec.injector.sidecar.port -- Listening port for the AppSec sidecar processor

port: 8080

# datadog.appsec.injector.sidecar.healthPort -- Health check port for the AppSec sidecar processor

healthPort: 8081

# datadog.appsec.injector.sidecar.bodyParsingSizeLimit -- Request body parsing size limit in bytes for the AppSec sidecar processor. Set to 0 to leave it unset (default agent behavior). Set to a negative value (e.g. -1) to disable body parsing entirely.

bodyParsingSizeLimit: 0

resources:

requests:

# datadog.appsec.injector.sidecar.resources.requests.cpu -- CPU request for the AppSec sidecar processor

cpu: "10m"

# datadog.appsec.injector.sidecar.resources.requests.memory -- Memory request for the AppSec sidecar processor

memory: "128Mi"

limits:

# datadog.appsec.injector.sidecar.resources.limits.cpu -- Optional CPU limit for the AppSec sidecar processor

cpu: ""

# datadog.appsec.injector.sidecar.resources.limits.memory -- Optional memory limit for the AppSec sidecar processor

memory: ""

processor:

# datadog.appsec.injector.processor.address -- Address of the AppSec processor service

# Defaults to `{service.name}.{service.namespace}.svc`

address: ""

# datadog.appsec.injector.processor.port -- Port of the AppSec processor service (defaults to 443)

port: 443

# datadog.appsec.injector.service -- Required service information to connect to the AppSec processor

# This service should point to a deployment of the image `ghcr.io/DataDog/dd-trace-go/service-extensions-callout:latest`

# This deployment is not managed by the Datadog Helm chart.

service:

# datadog.appsec.injector.processor.service.name -- Name of the AppSec processor service

name: ""

# datadog.appsec.injector.processor.service.namespace -- Namespace where the AppSec processor service is deployed

namespace: ""

nginx:

# datadog.appsec.injector.nginx.moduleMountPath -- Path inside the ingress-nginx controller pod where the nginx-datadog module .so is mounted from the shared emptyDir

moduleMountPath: "/modules_mount"

## OTLP ingest related configuration

otlp:

receiver:

protocols:

# datadog.otlp.receiver.protocols.grpc - OTLP/gRPC configuration

grpc:

# datadog.otlp.receiver.protocols.grpc.enabled -- Enable the OTLP/gRPC endpoint

enabled: false

# datadog.otlp.receiver.protocols.grpc.endpoint -- OTLP/gRPC endpoint

endpoint: "0.0.0.0:4317"

# datadog.otlp.receiver.protocols.grpc.useHostPort -- Enable the Host Port for the OTLP/gRPC endpoint

useHostPort: true

# datadog.otlp.receiver.protocols.http - OTLP/HTTP configuration

http:

# datadog.otlp.receiver.protocols.http.enabled -- Enable the OTLP/HTTP endpoint

enabled: false

# datadog.otlp.receiver.protocols.http.endpoint -- OTLP/HTTP endpoint

endpoint: "0.0.0.0:4318"

# datadog.otlp.receiver.protocols.http.useHostPort -- Enable the Host Port for the OTLP/HTTP endpoint

useHostPort: true

logs:

# datadog.otlp.logs.enabled -- Enable logs support in the OTLP ingest endpoint

enabled: false

## Host Profiler related configuration for the host-profiler in Agent Daemonset. Note this is experimental and subject to change

hostProfiler:

# datadog.hostProfiler.enabled -- Enable the Host Profiler. This feature is experimental and subject to change.

enabled: false

# datadog.hostProfiler.image -- Image the Host Profiler. This parameter is experimental and will be removed once official image is available.

image: ""

# datadog.hostProfiler.imagePullPolicy -- Pull policy for the Host Profiler image. Defaults to agents.image.pullPolicy when unset.

imagePullPolicy: ""

# datadog.hostProfiler.seccomp -- Seccomp profile configuration for the Host Profiler

seccomp:

# datadog.hostProfiler.seccomp.enabled -- Apply the localhost seccomp profile to the host-profiler container and run the init container that installs it on the node. Disable to run the host-profiler container Unconfined (no init container, no profile installed on the node).

enabled: true

# datadog.hostProfiler.seccompRoot -- Specify the seccomp profile root directory

seccompRoot: /var/lib/kubelet/seccomp

# datadog.hostProfiler.apparmor -- Specify an AppArmor profile for the host-profiler container (e.g. "localhost/datadog-host-profiler").

## Only used when agents.podSecurity.apparmor.enabled is true.

apparmor: unconfined

## OTel collector related configuration for the otel-agent in Agent Daemonset

otelCollector:

# datadog.otelCollector.enabled -- Enable the OTel Collector

enabled: false

# datadog.otelCollector.ports -- Ports that OTel Collector is listening on

ports:

# Default GRPC port of OTLP receiver

- containerPort: "4317"

name: otel-grpc

protocol: TCP

# Default HTTP port of OTLP receiver

- containerPort: "4318"

name: otel-http

protocol: TCP

# datadog.otelCollector.config -- OTel collector configuration

config: null

# datadog.otelCollector.configMap -- Use an existing ConfigMap for DDOT Collector configuration

configMap:

# datadog.otelCollector.configMap.name -- Name of the existing ConfigMap that contains the DDOT Collector configuration

name: null

# datadog.otelCollector.configMap.items -- Items within the ConfigMap that contain DDOT Collector configuration

items:

# - key: otel-config.yaml

# path: otel-config.yaml

# - key: otel-config-two.yaml

# path: otel-config-two.yaml

# datadog.otelCollector.configMap.key -- Key within the ConfigMap that contains the DDOT Collector configuration

key: otel-config.yaml

# datadog.otelCollector.featureGates -- Feature gates to pass to OTel collector, as a comma separated list

featureGates: null

# datadog.otelCollector.useStandaloneImage -- If true, the OTel Collector will use the `ddot-collector` image instead of the `agent` image

# The tag is retrieved from the `agents.image.tag` value.

# This is only supported for agent versions 7.67.0+

# If set to false, you will need to set `agents.image.tagSuffix` to `full`

useStandaloneImage: true

## Provide OTel Collector RBAC configuration

rbac:

# datadog.otelCollector.rbac.create -- If true, check OTel Collector config for k8sattributes processor

# and create required ClusterRole to access Kubernetes API

create: true

# datadog.otelCollector.rbac.rules -- A set of additional RBAC rules to apply to OTel Collector's ClusterRole

rules: []

# - apiGroups: [""]

# resources: ["pods", "nodes"]

# verbs: ["get", "list", "watch"]

## Provide OTel Collector logs configuration

logs:

# datadog.otelCollector.logs.enabled -- Enable logs support in the OTel Collector.

# If true, checks OTel Collector config for filelog receiver and mounts additional volumes to collect containers

# and pods logs.

enabled: false

## Continuous Profiler configuration

##

## Continuous Profiler is disabled by default and can be enabled by setting the `enabled` field to

## either `auto` or `true` value under the `datadog.profiling` section.

## Manually adding the `DD_PROFILING_ENABLED` variable to a pod will take precedence over the

## value in the Helm chart.

## These will only have an effect on containers that have Datadog client libraries installed,

## either manually or via Single Step Instrumentation (under the `datadog.apm.instrumentation`

## section).

## It requires Datadog Cluster Agent 7.57.0+.

profiling:

# datadog.profiling.enabled -- Enable Continuous Profiler by injecting `DD_PROFILING_ENABLED`

# environment variable with the same value to all pods in the cluster

# Valid values are:

# - false: Profiler is turned off and can not be turned on by other means.

# - null: Profiler is turned off, but can be turned on by other means.

# - auto: Profiler is turned off, but the library will turn it on if the application is a good candidate for profiling.

# - true: Profiler is turned on.

enabled: null

# datadog.envFrom -- Set environment variables for all Agents directly from configMaps and/or secrets

## envFrom to pass configmaps or secrets as environment

envFrom: []

# - configMapRef:

# name: <CONFIGMAP_NAME>

# - secretRef:

# name: <SECRET_NAME>

# datadog.env -- Set environment variables for the node Agents containers only

## The Datadog Agent supports many environment variables.

## ref: https://docs.datadoghq.com/agent/docker/?tab=standard#environment-variables

env: []

# - name: <ENV_VAR_NAME>

# value: <ENV_VAR_VALUE>

# datadog.envDict -- Set environment variables defined in a dict for node Agents containers only

envDict: {}

# <ENV_VAR_NAME>: <ENV_VAR_VALUE>

# datadog.confd -- Provide additional check configurations (static and Autodiscovery)

## Each key becomes a file in /conf.d

## ref: https://github.com/DataDog/datadog-agent/tree/main/Dockerfiles/agent#optional-volumes

## ref: https://docs.datadoghq.com/agent/autodiscovery/

confd: {}

# redisdb.yaml: |-

# init_config:

# instances:

# - host: "name"

# port: "6379"

# kubernetes_state.yaml: |-

# ad_identifiers:

# - kube-state-metrics

# init_config:

# instances:

# - kube_state_url: http://%%host%%:8080/metrics

# datadog.checksd -- Provide additional custom checks as python code

## Each key becomes a file in /checks.d

## ref: https://github.com/DataDog/datadog-agent/tree/main/Dockerfiles/agent#optional-volumes

checksd: {}

# service.py: |-

# datadog.dockerSocketPath -- Path to the docker socket

dockerSocketPath: # /var/run/docker.sock

# datadog.criSocketPath -- Path to the container runtime socket (if different from Docker)

criSocketPath: # /var/run/containerd/containerd.sock

# Configure how the agent interact with the host's container runtime

containerRuntimeSupport:

# datadog.containerRuntimeSupport.enabled -- Set this to false to disable agent access to container runtime.

enabled: true

## Enable process agent and provide custom configs

processAgent:

# datadog.processAgent.enabled -- Set this to true to enable live process monitoring agent

# DEPRECATED. Set `datadog.processAgent.processCollection` or `datadog.processAgent.containerCollection` instead.

## Note: /etc/passwd is automatically mounted when `processCollection`, `processDiscovery`, or `containerCollection` is enabled.

## ref: https://docs.datadoghq.com/graphing/infrastructure/process/#kubernetes-daemonset

enabled: true

# datadog.processAgent.processCollection -- Set this to true to enable process collection

processCollection: false

# datadog.processAgent.stripProcessArguments -- Set this to scrub all arguments from collected processes

## Requires datadog.processAgent.processCollection to be set to true to have any effect

## ref: https://docs.datadoghq.com/infrastructure/process/?tab=linuxwindows#process-arguments-scrubbing

stripProcessArguments: false

# datadog.processAgent.processDiscovery -- Enables or disables autodiscovery of integrations

processDiscovery: true

# datadog.processAgent.runInCoreAgent -- Set this to true to run the following features in the core agent: Live Processes, Live Containers, Process Discovery.

## This requires Agent 7.60.0+ and Linux.

## DEPRECATED: This behavior will be enabled by default for installations that meet the requirements.

## For Agent 7.78.0+, this setting is ignored — process checks always run in the core agent on Linux.

runInCoreAgent: true

# datadog.processAgent.containerCollection -- Set this to true to enable container collection

## ref: https://docs.datadoghq.com/infrastructure/containers/?tab=helm

containerCollection: true

# datadog.disableDefaultOsReleasePaths -- Set this to true to disable mounting datadog.osReleasePath in all containers

disableDefaultOsReleasePaths: false

# datadog.disablePasswdMount -- Set this to true to disable mounting /etc/passwd in all containers

disablePasswdMount: false

# datadog.osReleasePath -- Specify the path to your os-release file

osReleasePath: /etc/os-release

## Enable systemProbe agent and provide custom configs

systemProbe:

# datadog.systemProbe.debugPort -- Specify the port to expose pprof and expvar for system-probe agent

debugPort: 0

# datadog.systemProbe.enableConntrack -- Enable the system-probe agent to connect to the netlink/conntrack subsystem to add NAT information to connection data