Skip to content

Latest commit

 

History

History
96 lines (72 loc) · 3.45 KB

getting_started.md

File metadata and controls

96 lines (72 loc) · 3.45 KB

Getting Started

This page describes a simple and fast way to deploy the Datadog Agent with the Operator. For more details on how to install the Operator and configure the Agent it deploys, refer to the installation guide.

Prerequisites

Using the Datadog Operator requires the following prerequisites:

  • Kubernetes Cluster version >= v1.20.X: Tests were performed on Kubernetes versions >= 1.20.0. It is expected to work on versions >= v1.11.0, but for earlier versions the Operator may not work as expected because of limited CRD support.
  • Helm for deploying the Datadog Operator
  • kubectl CLI for installing the Datadog Agent

Deploy the Agent with the Operator

To deploy the Datadog Agent with the Operator using a minimum number of steps, use the datadog-operator Helm chart.

  1. Install the Datadog Operator:

    helm repo add datadog https://helm.datadoghq.com
helm install my-datadog-operator datadog/datadog-operator

  2. Create a Kubernetes Secret with your API and application keys:

    kubectl create secret generic datadog-secret --from-literal api-key=<DATADOG_API_KEY> --from-literal app-key=<DATADOG_APP_KEY>

    Replace <DATADOG_API_KEY> and <DATADOG_APP_KEY> with your Datadog API and application keys.

  3. Create a file with the spec of your DatadogAgent deployment configuration. The simplest configuration is:

    apiVersion: datadoghq.com/v2alpha1
kind: DatadogAgent
metadata:
  name: datadog
spec:
  global:
    credentials:
      apiSecret:
        secretName: datadog-secret
        keyName: api-key
      appSecret:
        secretName: datadog-secret
        keyName: app-key

  4. Deploy the Datadog Agent with the above configuration file:

    kubectl apply -f /path/to/your/datadog-agent.yaml

Installation options

The configuration page lists all the Datadog Agent and Cluster Agent features and options that can be configured with the DatadogAgent resource.

Configure integrations

Visit the Integrations Autodiscovery page for details about how to configure Agent Integrations when using the Datadog Operator.

Containers registry

To change the default registry (gcr.io/datadoghq) to another registry, use the option spec.global.registry.

The example datadog-agent-with-registry.yaml file demonstrates how to configure the Operator to use the public.ecr.aws/datadog registry.

apiVersion: datadoghq.com/v2alpha1
kind: DatadogAgent
metadata:
  name: datadog
spec:
  global:
    registry: public.ecr.aws/datadog
  # ...

Cleanup

The following command deletes all the Kubernetes resources created by the above instructions:

kubectl delete datadogagent datadog
helm delete my-datadog-operator