> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/self-managed-cloud-platform/5.7/cluster-internals.md).
# Cluster Internals
This article describes the overall architecture for Platform9 Edge Cloud.
Platform9 Edge Cloud consists of three major components that make up the product:
* **The Management Plane (Deployment Unit (DU))**: This is the main element that provides component management
* **Host Components**: These are cluster elements that make management of the Kubernetes cluster possible.
* **Utilities:** The CLI that aids in setting up the management Plane (only applicable to the air-gapped version)
The illustration below is an approximate overview of the configured architecture. It is divided into two main types of hardware:
* A management workstation
* The cluster machines
* **Management Machine**: The management workstation contains the management plane, the component which provides APIs for managing clusters, and the utilities used to manage the different nodes. Further details can be found on the [auto$](https://github.com/platform9/pcd-docs-gitbook/blob/main/PEC/management-plane/README.md) page.
* **Cluster Machines**: Typically, these machines are managed remotely and contain all the elements needed for the cluster creation. Further details on the cluster internals can be found on the [auto$](https://github.com/platform9/pcd-docs-gitbook/blob/main/PEC/host-internals/README.md) page.
---
# 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.platform9.com/self-managed-cloud-platform/5.7/cluster-internals.md?ask=&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.
