> For the complete documentation index, see [llms.txt](https://docs.apolo.us/index/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apolo.us/index/administration/managed-kubernetes/architecture-and-features.md).

# Architecture & Features

#### Control Plane

\- Highly available master nodes with automated backups.\
\- Deployed on dedicated nodes within the same data center as worker nodes for optimal latency.

#### Data Plane

\- Worker nodes provisioned to match workload-specific requirements.\
\- Flexible GPU and CPU profiles for AI/ML workloads.

#### Load Balancer Provisioning

\- Kubernetes \`LoadBalancer\` Services trigger either automated provisioning (in fully integrated environments) or rapid manual configuration by our team.

#### Storage

\- Optional \`StorageClass\` backed by OpenEBS or data center–native block storage solutions.

#### Observability

\- Continuous monitoring of control plane, data plane, and underlying resources.\
\- Automated alerts for degraded conditions, handled by Apolo operations.

#### Security

\- CNI with NetworkPolicies support.\
\- etcd encryption at rest.\
\- Optional OIDC IdP integration for authentication and RBAC.

\\


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.apolo.us/index/administration/managed-kubernetes/architecture-and-features.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.