Quick Guide for Datadog Agent on Kubernetes for Infrastructure

The Datadog Agent on Kubernetes collects infrastructure metrics, logs, and traces from your cluster and its workloads. This guide provides the steps to deploy and configure the agent using Helm, including how to enable pod-level metric collection through annotations and orchestrator monitoring. Use this guide to get the agent up and running with your Kubernetes environment.

Add the Datadog Helm repository

helm repo add datadog https://helm.datadoghq.com
helm repo update

Configure `datadog-values.yaml`

For pod-level metrics, add Datadog annotations to enable scraping.

Base configuration

fullnameOverride: "kfuse-agent"
nameOverride: "kfuse-agent"
datadog:
  apiKey: " "
  #
  # Scenario default: Assumes that Kloudfuse stack & agent both in same VPC and in same K8S cluster
  #
  dd_url: "http://kfuse-ingress-nginx-controller-internal.kfuse/ingester"
  #
  # Scenario 1: Kloudfuse stack & agent both in same VPC, but in different K8S cluster
  #
  # dd_url: "http://<ingress-ip>/ingester"
  #
  # Scenario 2: Kloudfuse stack hosted in a different VPC (hosted at “customer.kloudfuse.io”)
  #
  # dd_url: "https://customer.kloudfuse.io/ingester"
  #

yaml

Enable orchestrator

...
datadog:
  ...
  orchestratorExplorer:
    enabled: true

clusterAgent:
  datadog_cluster_yaml:
    orchestrator_explorer:
      #
      # Scenario default: Assumes that Kloudfuse stack & agent both in same VPC and in same K8S cluster
      #
      orchestrator_dd_url: "http://kfuse-ingress-nginx-controller-internal.kfuse"
      #
      # Scenario 1: Kloudfuse stack & agent both in same VPC, but in different K8S cluster
      #
      # orchestrator_dd_url: "http://<ingress-ip>"
      #
      # Scenario 2: Kloudfuse stack hosted in a different VPC (hosted at “customer.kloudfuse.io”)
      #
      # orchestrator_dd_url: "https://customer.kloudfuse.io"
      #
agents:
  customAgentConfig:
    ...
    orchestrator_explorer:
      #
      # Scenario default: Assumes that Kloudfuse stack & agent both in same VPC and in same K8S cluster
      #
      orchestrator_dd_url: "http://kfuse-ingress-nginx-controller-internal.kfuse"
      #
      # Scenario 1: Kloudfuse stack & agent both in same VPC, but in different K8S cluster
      #
      # orchestrator_dd_url: "http://<ingress-ip>"
      #
      # Scenario 2: Kloudfuse stack hosted in a different VPC (hosted at “customer.kloudfuse.io”)
      #
      # orchestrator_dd_url: "https://customer.kloudfuse.io"
      #