You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/integrations/kubernetes.md
+39-1Lines changed: 39 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,9 +5,47 @@ kind: integration
5
5
git_integration_title: kubernetes
6
6
---
7
7
8
+
# Overview
9
+
8
10
Get metrics from your Kubelets in real time to:
9
11
10
-
* Visualize your Kubernetes cluster performance
12
+
* Vizualize your Kubernetes cluster performance
13
+
* Collect performances metrics for your containers, pods, container namespaces
14
+
* Create monitors on the status of your Kubelets
15
+
* Ingest Kubernetes labels as tags in Datadog.
16
+
17
+
# Installation
18
+
19
+
The Kubernetes integration is deployed as a docker container along side your existing workloads.
20
+
21
+
## Installation via DaemonSets (Kubernetes >=1.1.0)
22
+
23
+
If you are running Kubernetes >= 1.2.0, you can take advantage of DaemonSets to automatically deploy the Datadog Agent on all your nodes. On clusters running 1.1.x you will need to explicitly [enable the DaemonSets extension](http://kubernetes.io/v1.1/docs/admin/daemons.html#caveats).
24
+
25
+
1. Download the [dd-agent.yaml](https://app.datadoghq.com/account/settings#agent/kubernetes) manifest file.
26
+
1. Launch dd-agent:
27
+
kubectl create -f dd-agent.yaml
28
+
29
+
## Manual Installation
30
+
31
+
If DaemonSets are not an option for your Kubernetes cluster, you will need to install the Datadog agent as a sidecar container on each Kubernetes node.
If you would like to customize your Agent configuration, please refer to the Agent [container documentation](https://github.com/DataDog/docker-dd-agent).
38
+
39
+
# Validation
40
+
41
+
To verify the Datadog agent is running in your environment as a daemonset, execeute:
42
+
43
+
$ kubectl get daemonset
44
+
45
+
If the agent is deployed you will see similar output to the text below, where desired and current are equal to the number of running nodes in your cluster.
0 commit comments