Index of every page on this site: llms.txt
All skills
datadog-labs avatar

/dd-agent-install-kubernetes

@618fae3 official
Run it yourself

Install the Datadog Agent on a Kubernetes cluster - Amazon EKS (standard or Fargate profiles), Azure AKS, Google GKE (standard or Autopilot), OpenShift, Oracle OKE, VMware Tanzu (TKG), Rancher (RKE2/K3s), or self-managed - through the Datadog Operator (kubectl/Helm), the Datadog Helm chart, or Terraform, with metrics, logs, and APM trace intake on by default, Single Step Instrumentation off unless the user asks, and optional products; for an SSI-first install use `dd-apm/k8s-ssi` `agent-install`. Use when the user is running a Kubernetes cluster on GKE, EKS, AKS, OpenShift, OKE, or TKG, asks to install or set up the Datadog Agent on Kubernetes, wants to install the Agent with Terraform, or wants to monitor their Kubernetes pods. Does not connect a cloud provider integration or install the Agent on standalone hosts or plain Docker. Requires a Datadog account with a valid API key and application key; run `dd-account-setup` first if they are missing.

Use this Skill: https://skilld.dev/gh/datadog-labs/agent-skills/dd-agent-install-kubernetes

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesadvanced.md

≈1.6k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Advanced configuration

APM Single Step Instrumentation (with library pinning and namespace scoping), FIPS mode, and private registries. Use these only when the user selected them in SKILL.md Phase 1.

APM Single Step Instrumentation, library pinning, and namespace scoping

Only when the user explicitly opted in to Single Step Instrumentation. Use the namespace allowlist / denylist and any verified tracer versions captured in SKILL.md Phase 1.

Operator path (merge into spec.features)

apm:
  enabled: true
  instrumentation:
    enabled: true
    disabledNamespaces:
      - <NS_TO_SKIP>
    targets:
      - name: default-target
        namespaceSelector:
          matchNames:
            - <NS1>
            - <NS2>
        ddTraceVersions:
          java: "<VERIFIED_VERSION>"
          python: "<VERIFIED_VERSION>"
          js: "<VERIFIED_VERSION>"
          dotnet: "<VERIFIED_VERSION>"
          ruby: "<VERIFIED_VERSION>"
        ddTraceConfigs:
          - name: DD_PROFILING_ENABLED
            value: auto

Drop ddTraceVersions when no versions were pinned. Drop namespaceSelector when no allowlist was given. Drop disabledNamespaces when no denylist was given. Drop ddTraceConfigs unless the user selected profiling or another tracer configuration.

Install the Datadog Agent in the separate datadog namespace. Single Step Instrumentation does not instrument applications in the Agent's own namespace. Profiling is a separate user choice.

Helm chart path

datadog:
  apm:
    instrumentation:
      enabled: true
      disabledNamespaces:
        - <NS_TO_SKIP>
      targets:
        - name: default-target
          namespaceSelector:
            matchNames:
              - <NS1>
              - <NS2>
          ddTraceVersions:
            java: "<VERIFIED_VERSION>"
            python: "<VERIFIED_VERSION>"
            js: "<VERIFIED_VERSION>"
            dotnet: "<VERIFIED_VERSION>"
            ruby: "<VERIFIED_VERSION>"
          ddTraceConfigs:
            - name: DD_PROFILING_ENABLED
              value: auto

FIPS mode

Operator path

Add to spec.global:

useFIPSAgent: true

Confirm the Datadog organization uses a currently supported FED site, the selected nodes and cloud region meet the FIPS requirements, and the chosen Agent version supports the FIPS image before applying this setting. Verify those conditions against the current FIPS supported-platform documentation; the presence of the value alone does not mean the selected distribution, mode, region, and products are supported.

Helm chart path

useFIPSAgent: true

Private registries

Operator image (Operator path and Terraform)

For a restricted-network install, mirror the Operator image as well as the Agent images. The DatadogAgent registry setting does not affect the Operator deployment. Ensure the pull secret already exists in the datadog namespace, then create datadog-operator-values.yaml:

image:
  repository: <PRIVATE_REGISTRY_PREFIX>/operator
imagePullSecrets:
  - name: <PULL_SECRET_NAME>

Kubernetes Secrets are namespace-scoped. Do not ask for a registry password in chat or place it on a command line; create the datadog namespace first, then use the user's approved secret-management workflow to create the secret. Add -f datadog-operator-values.yaml to the install command when using the private mirror.

Operator path (DatadogAgent)

The registry URL is a spec.global field, but the DatadogAgent CRD exposes pull secrets per-component via pullSecrets on each override.<component>.image block (not as a global imagePullSecrets). Set the registry once globally, then attach the same pull secret on every component that pulls the agent image:

spec:
  global:
    registry: <PRIVATE_REGISTRY_HOST>/datadog
  override:
    nodeAgent:
      image:
        pullSecrets:
          - name: <PULL_SECRET_NAME>
    clusterAgent:
      image:
        pullSecrets:
          - name: <PULL_SECRET_NAME>
    clusterChecksRunner:
      image:
        pullSecrets:
          - name: <PULL_SECRET_NAME>

Drop the clusterChecksRunner block if cluster-check runners aren't enabled.

The blocks above only cover the Agent components. When APM Single Step Instrumentation is enabled, the admission controller also injects an apm-inject init container and per-language tracer init containers (dd-lib-java-init, dd-lib-python-init, dd-lib-js-init, dd-lib-dotnet-init, dd-lib-ruby-init, dd-lib-php-init) that pull from gcr.io/datadoghq by default - a public registry a restricted-network cluster can't reach. Mirror the images for the languages in use, then point the admission controller at the mirror through its first-class registry field:

spec:
  features:
    admissionController:
      registry: <PRIVATE_REGISTRY_HOST>/datadog

For EKS Fargate, also set spec.features.admissionController.agentSidecarInjection.registry to the same mirror explicitly. Mirrored tracer image tags must match the requested ddTraceVersions (an unset version resolves to tag 0). The registry override changes image locations but does not provide credentials to the injected workload. Ensure the pull secret exists in every namespace selected for Single Step Instrumentation and that each workload service account references it through imagePullSecrets. Ask before patching a shared or default service account.

Helm chart path

registry: <PRIVATE_REGISTRY_HOST>/datadog
agents:
  image:
    pullSecrets:
      - name: <PULL_SECRET_NAME>
clusterAgent:
  image:
    pullSecrets:
      - name: <PULL_SECRET_NAME>
clusterChecksRunner:
  image:
    pullSecrets:
      - name: <PULL_SECRET_NAME>

With APM Single Step Instrumentation enabled, also mirror the injection images (apm-inject and the dd-lib-<lang>-init tracer init containers for the languages in use, which default to gcr.io/datadoghq) and point the admission controller at the mirror:

clusterAgent:
  admissionController:
    containerRegistry: <PRIVATE_REGISTRY_HOST>/datadog

Ensure the pull secret exists in every namespace selected for Single Step Instrumentation and that each workload service account references it through imagePullSecrets. Ask before patching a shared or default service account. The same requirement applies to Fargate workload namespaces because the injected Agent sidecar is pulled by the workload pod.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning8d3 checks · Risk SAFE
  • Gen Agent Trust Hub8d

    This skill provides a robust and secure method for installing the Datadog Agent across various Kubernetes distributions. It adheres to security best practices for credential management, utilizes trusted sources for configuration data, and incorporates mandatory user-confirmation steps before executing any modifications to the target environment.

  • Socket8d

    No alerts

  • Snyk8d

    Risk: MEDIUM · 1 issue

Signed by skilld at 618fae3. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated last week
Other metadata
metadata
{
  "version": "1.0.3",
  "author": "datadog-labs",
  "repository": "https://github.com/datadog-labs/agent-skills",
  "tags": "datadog,agent,kubernetes,k8s,eks,aks,gke,openshift,oke,tkg,rancher,terraform",
  "alwaysApply": "false",
  "tools": "kubectl,oc,helm,terraform,aws,az,gcloud,oci,openssl"
}

README badge

README badge for datadog-labs/agent-skills/dd-agent-install-kubernetes