|
1 | 1 | Architecture |
2 | 2 | ================== |
3 | 3 |
|
4 | | -The base installation for Robusta runs in-cluster as two Kubernetes deployments |
| 4 | +Robusta follows a modular architecture designed to integrate seamlessly with your existing Kubernetes observability stack. The system consists of core components that run in-cluster and optional components for enhanced functionality. |
5 | 5 |
|
6 | | -* robusta-forwarder - Connects to the APIServer and monitors Kubernetes changes. Forwards them to robusta-runner. |
7 | | -* robusta-runner - Receives all events, evaluates playbooks, sends notifications |
| 6 | +Core Components |
| 7 | +^^^^^^^^^^^^^^^ |
| 8 | + |
| 9 | +Robusta's core architecture runs entirely within your Kubernetes cluster: |
| 10 | + |
| 11 | +**robusta-forwarder** |
| 12 | + A lightweight deployment that connects to the Kubernetes APIServer to monitor cluster events and resource changes. It forwards relevant events to the runner component for processing. This component ensures Robusta stays up-to-date with your cluster state in real-time. |
| 13 | + |
| 14 | +**robusta-runner** |
| 15 | + The main processing engine that receives events from the forwarder, evaluates playbook rules, executes enrichment actions, and sends notifications to configured destinations. It contains the business logic for alert correlation, data enrichment, and routing decisions. |
8 | 16 |
|
9 | 17 | .. image:: ../images/arch-1/arch-1.png |
10 | 18 | :width: 600 |
11 | 19 | :align: center |
12 | 20 |
|
13 | | -Optionally, Robusta has some additional components, described below. |
| 21 | +Data Flow |
| 22 | +^^^^^^^^^ |
14 | 23 |
|
15 | | -HolmesGPT (Optional) |
16 | | -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
17 | | -Robusta's next generation AI-engine that investigates alerts automatically. See :ref:`AI Analysis <AI Analysis>`. |
| 24 | +1. **Event Collection**: The forwarder monitors Kubernetes APIServer for resource changes and forwards them to the runner |
| 25 | +2. **Alert Processing**: Prometheus AlertManager webhooks are received by the runner for alert enrichment |
| 26 | +3. **Playbook Execution**: The runner evaluates configured playbooks and triggers appropriate actions |
| 27 | +4. **Enrichment**: Additional context is gathered (logs, metrics, resource states) and attached to alerts |
| 28 | +5. **Routing**: Enriched alerts are routed to configured sinks (Slack, Teams, etc.) based on routing rules |
18 | 29 |
|
19 | | -Bundled Prometheus (Optional) |
20 | | -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
| 30 | +Extended Architecture |
| 31 | +^^^^^^^^^^^^^^^^^^^^ |
21 | 32 |
|
22 | | -Install Robusta with :ref:`Prometheus included <embedded Prometheus stack>`. This is powered by ``kube-prometheus-stack``. |
| 33 | +**AI Analysis with HolmesGPT** |
| 34 | + Robusta's AI engine automatically investigates alerts by analyzing logs, events, and cluster state to provide root cause analysis and remediation suggestions. See :ref:`AI Analysis <AI Analysis>` for configuration details. |
23 | 35 |
|
24 | | -Alternatively, you can :ref:`integrate an existing Prometheus with Robusta <Integrating with Prometheus>`. |
| 36 | +**Prometheus Integration** |
| 37 | + Robusta can work with your existing Prometheus setup or be installed with a :ref:`bundled Prometheus stack <embedded Prometheus stack>` powered by ``kube-prometheus-stack``. The integration enables automatic alert enrichment and correlation. |
25 | 38 |
|
26 | | -Web UI (Optional) |
27 | | -^^^^^^^^^^^^^^^^^^^^^^ |
| 39 | +**Centralized Management** |
| 40 | + The Robusta `SaaS platform <http://home.robusta.dev/?from=docs>`_ provides centralized alert management, historical analysis, and cross-cluster visibility. Self-hosted options are available for enterprise deployments. |
28 | 41 |
|
29 | | -The Robusta `SaaS platform <http://home.robusta.dev/?from=docs>`_ provides a single pane of glass for all your alerts and clusters. |
| 42 | +**CLI Tooling** |
| 43 | + The ``robusta`` CLI simplifies installation and configuration management by auto-generating Helm values and providing cluster diagnostics. |
30 | 44 |
|
31 | | -On commercial plans, the UI is available for self-hosting in your own environment. |
| 45 | +Security & Networking |
| 46 | +^^^^^^^^^^^^^^^^^^^^^ |
32 | 47 |
|
33 | | -CLI (Optional) |
34 | | -^^^^^^^^^^^^^^^^ |
35 | | -The ``robusta`` cli makes it easier to install Robusta by auto-generating Helm values. |
| 48 | +* All core components run within your cluster with configurable RBAC permissions. |
| 49 | +* External integrations use secure webhook endpoints with optional authentication. |
| 50 | +* SaaS connectivity is outbound-only with no inbound access required. |
| 51 | +* All data remains in your cluster unless explicitly sent to configured sinks e.g. Slack, Robusta UI. |
36 | 52 |
|
37 | 53 | Next Steps |
38 | | -^^^^^^^^^^^^^ |
| 54 | +^^^^^^^^^^ |
39 | 55 |
|
40 | 56 | :ref:`Ready to install Robusta? Get started. <install>` |
0 commit comments