datadog-operator

README

Datadog Operator

This project is currently in Beta

Overview

The Datadog Operator aims to provide a new way of deploying the Datadog Agent on Kubernetes. Once deployed, the Datadog Operator provides:

• Agent configuration validation that limits configuration mistakes.
• Orchestration of creating/updating Datadog Agent resources.
• Reporting of Agent configuration status in its Kubernetes CRD resource.
• Optionally, use of an advanced DaemonSet deployment by leveraging the ExtendedDaemonSet.
• Many other features to come :).

Datadog Operator vs. Helm chart

The official Datadog Helm chart is still the recommended way to setup Datadog in a Kubernetes cluster, as it has most supported configuration options readily accessible. It also makes using more advanced features easier than rolling your own deployments.

The Datadog Operator aims to improve the user experience around deploying Datadog. It does this by reporting deployment status, health, and errors in its Custom Resource status, and by limiting the risk of misconfiguration thanks to higher-level configuration options.

However, the Datadog Operator is still in alpha, so it is not yet a recommended way of installing the Agent in production. Datadog's end goal is to support both the Helm chart and the operator (as well as providing basic deployment files in the Agent repository when CRDs and Helm are not an option) as official ways of installing Datadog.

Getting started

See the Getting Started dedicated documentation to learn how to deploy the Datadog operator and your first Agent.

Functionnalities

The Datadog operator also allows you to:

• Configure and provide custom checks to the Agents.
• Deploy the Datadog Cluster Agent with your node Agents.

How to contribute

See the How to Contribute page.

Release

Release process documentation is available here.