> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/deployment/kubernetes/server/components.md).

# Components

Overview of the core systems behind Bindplane's architecture, including NATS for messaging, Kubernetes Ingress for routing, and PostgreSQL for stateful storage.

Bindplane Server relies on several key components when deployed on Kubernetes:

## Core Components

### [Event Bus](/deployment/kubernetes/server/components/event-bus.md)

NATS provides the messaging backbone for Bindplane, enabling reliable communication between server instances and collectors. It handles configuration updates, heartbeats, and telemetry routing.

### [Kubernetes Ingress](/deployment/kubernetes/server/components/kubernetes-ingress.md)

The Ingress controller manages external access to Bindplane services, providing TLS termination, load balancing, and routing capabilities for both the UI and API endpoints.

### [PostgreSQL](/deployment/kubernetes/server/components/postgresql.md)

PostgreSQL serves as the primary stateful storage for Bindplane, maintaining configuration data, collector registrations, user information, and audit logs in a reliable and scalable database.

These components work together to provide a resilient, scalable platform for managing your telemetry pipeline. Each can be configured and scaled independently to meet your specific requirements.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bindplane.com/deployment/kubernetes/server/components.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.