master
md 72 lines 3.79 KB
Rendered Raw
1 # Deployment Guides
2
3 Get Netdata up and running in your infrastructure. Choose a deployment method that fits your needs.
4
5 ## Quick Start
6
7 :::tip Getting Started
8
9 - **Testing Netdata?**[Docker deployment](/packaging/docker/README.md) (2 minutes, easy cleanup)
10 - **Monitoring one server?**[Standalone installation](/docs/deployment-guides/standalone-deployment.md) (1 minute, upgradeable)
11 - **Production ready?**[Parent-Child setup](/docs/deployment-guides/deployment-with-centralization-points.md) (recommended)
12
13 :::
14
15 ## Deployment Methods
16
17 ### Standalone
18
19 Single Netdata Agent monitoring one system. Perfect for getting started or monitoring individual servers.
20
21 **Best for:** Testing or simple single-server monitoring
22
23 **Setup time:** < 1 minute
24
25 [→ Deploy Standalone Agent](/docs/deployment-guides/standalone-deployment.md)
26
27 ### Parent-Child Streaming (Recommended)
28
29 The recommended production setup. Stream metrics from Child Agents to centralized Parent nodes for better data persistence and resource optimization.
30
31 **Best for:** Production environments of any size, high availability requirements
32
33 **Setup time:** 10-15 minutes
34
35 [→ Deploy Parent-Child Setup](/docs/deployment-guides/deployment-with-centralization-points.md)
36
37 ### Kubernetes
38
39 Deploy Netdata across your Kubernetes clusters with our Helm chart. Required for proper Kubernetes monitoring.
40
41 **Best for:** Kubernetes environments (required for full K8s observability)
42
43 **Setup time:** 5-10 minutes
44
45 [→ Deploy on Kubernetes](https://github.com/netdata/helmchart#netdata-helm-chart-for-kubernetes-deployments)
46
47 ### Docker
48
49 Run Netdata in containers for quick testing. Note: Some features are limited compared to host installation.
50
51 **Best for:** Quick testing, ephemeral environments
52
53 **Setup time:** 2-5 minutes
54
55 [→ Deploy with Docker](/packaging/docker/README.md)
56
57 ## Which Deployment Should I Choose?
58
59 | Environment | Recommended Method | Why |
60 |-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|
61 | **Production servers** | [Parent-Child](/docs/deployment-guides/deployment-with-centralization-points.md) | Best data persistence, resource optimization, and high availability |
62 | **Kubernetes** | [Helm Chart](https://github.com/netdata/helmchart#netdata-helm-chart-for-kubernetes-deployments) | Required for K8s API access and pod metadata collection |
63 | **Testing/Development** | [Standalone](/docs/deployment-guides/standalone-deployment.md) or [Docker](/packaging/docker/README.md) | Quick setup, easy to remove |
64 | **Single server** | [Standalone](/docs/deployment-guides/standalone-deployment.md) (upgrade to [Parent-Child](/docs/deployment-guides/deployment-with-centralization-points.md) later) | Start simple, upgrade when ready for production |
65
66 :::warning Important Notes
67
68 - **Kubernetes**: Always use our Helm chart. Direct host installation won't have access to K8s API for pod metadata and service discovery.
69 - **Docker**: Limited feature set compared to host installation. Best for testing, not recommended for production.
70 - **Production**: Parent-Child is recommended regardless of cluster size for better reliability and data persistence.
71
72 :::