docs: agent mode / deployment modes

docs/docs-content/deployment-modes/_category_.json

@@ -0,0 +1,3 @@
+{
+  "position": 50
+}

docs/docs-content/deployment-modes/agent-mode/_category_.json

@@ -0,0 +1,3 @@
+{
+  "position": 20
+}

docs/docs-content/deployment-modes/agent-mode/agent-mode.md

@@ -0,0 +1,65 @@
+---
+sidebar_label: "Agent Mode"
+title: "Agent Mode"
+description: "Learn about agent mode, its use cases, and how to deploy a cluster in agent mode. "
+hide_table_of_contents: false
+sidebar_position: 20
+tags: ["edge"]
+---
+
+In agent mode, you bring your own host, which can be any host that meets the minimum hardware requirements, regardless
+of the environment. This includes options like an AWS EC2 instance or a Raspberry Pi in your own home. All you need to
+do to have Palette manage your host is to [download and install the Palette agent](./install-agent-host.md).
+
+:::preview
+
+:::
+
+The diagram below illustrates the agent mode cluster provisioning workflow.
+
+![Architecture Diagram for Agent Mode](/deployment-modes_agent-mode.webp)
+
+The order of operations can be summarized as follows:
+
+1. You provide a host as well as an Operating System (OS) that will operate on your host.
+
+2. You install the Palette agent on your host. Alternatively, you may build the Palette agent into your OS image.
+
+3. You create a cluster profile in Palette. The profile contains the Kubernetes distribution, the Container Network
+   Interface (CNI), the Container Storage Interface (CSI) as well as any other applications.
+
+4. If the agent is installed on your host in connected mode, it will register the host with Palette.
+
+   If the agent is installed on your host in airgap mode, you will need to export the cluster profile. Depending on
+   whether your host has access to image registries, you may also need to build a content bundle.
+
+5. If the agent is installed on your host in connected mode, you can use the registered host to provision a cluster with
+   your cluster profile.
+
+   If the agent is installed on your host in airgap mode, you can use the exported cluster profile to provision a
+   cluster from Local UI.
+
+## Use Cases
+
+Agent mode is designed to work across a variety of environments, including public clouds, on-prem data centers, and Edge
+locations. Currently, the validated use case for agent mode includes [Edge](../../clusters/edge/edge.md).
+
+| Use Case | Supported Environments                                                                                                  |
+| -------- | ----------------------------------------------------------------------------------------------------------------------- |
+| **Edge** | [VMware vSphere](../../clusters/edge/site-deployment/virtual-deployment/virtual-deployment.md)<br />Bare metal machines |
+
+## Next Steps
+
+Review the architecture and basic hardware requirements for operating clusters in agent mode in
+[Architecture](./architecture.md).
+
+Follow the instructions in [Install Palette Agent](install-agent-host.md) to install the agent on your host and deploy
+your first agent-mode cluster.
+
+## Resources
+
+- [Architecture](./architecture.md)
+
+- [Install Palette Agent](install-agent-host.md)
+
+- [Manage Hosts in Agent Mode](./manage-agent/manage-agent.md)

docs/docs-content/deployment-modes/agent-mode/architecture.md

@@ -0,0 +1,41 @@
+---
+sidebar_label: "Architecture"
+title: "Agent Mode Architecture"
+description: "Learn about the architecture of agent mode and its minimal hardware requirements."
+hide_table_of_contents: false
+sidebar_position: 20
+tags: ["edge"]
+---
+
+The following are architectural highlights of clusters deployed using agent mode.
+
+- You can bring an existing host with an Operating System (OS) of your choice.
+
+- You may also build the Palette agent into your OS image to have the agent natively installed on your host.
+
+- Support for bare metal, public clouds, data centers, and Edge devices.
+
+- Support for single-node and multi-node deployments.
+
+- Customizable site properties such as network proxies and certificates for Edge deployments.
+
+- Configurable Kubernetes API servers to work with virtual IP address (VIP) or Dynamic DNS.
+
+![Architecture Diagram for Agent Mode](/deployment-modes_agent-mode.webp)
+
+## Supported Kubernetes Distributions
+
+| Distribution | Versions                |
+| ------------ | ----------------------- |
+| PXK-E        | 1.28.13, 1.28.9, 1.30.5 |
+| K3s          | 1.28.14, 1.28.9, 1.30.5 |
+
+## Minimum Device Requirements
+
+Agent mode deployments support both AMD64 and ARM64 architectures.
+
+| Component | Requirement                                                                                                                                               |
+| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| CPU Core  | Minimum two cores.                                                                                                                                        |
+| Memory    | Minimum 8 GB.                                                                                                                                             |
+| Storage   | Main drive requires a minimum of 100 GB storage to accommodate the Operating System (OS), Kubernetes, and workloads. The main drive must be an SSD drive. |