Quick Guide for Datadog Agent on Kubernetes for Infrastructure

  1. Add the Datadog Helm repository.

    helm repo add datadog https://helm.datadoghq.com
    helm repo update
  2. Configure datadog-values.yaml.

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

  3. 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
  4. 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"
          #
    yaml
  5. Deploy the agent with the configuration file.

    helm install datadog-agent -f datadog-values.yaml datadog/datadog
  6. Verify that the agent runs in the cluster, and that data flows into Kloudfuse.