> ## Documentation Index
> Fetch the complete documentation index at: https://docs.acornops.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Kubernetes quick start

> Create a workspace, connect a Kubernetes cluster, and start your first chat

This quick start assumes AcornOps is deployed and you are connecting your first Kubernetes cluster.

## Before you begin

You need:

* Helm and `kubectl` access to the cluster.

## 1. Create a workspace

Sign in to the management console and select **Create New Workspace**.

1. Enter a workspace name.
2. Optionally invite members now, or continue without adding anyone.
3. If no platform AI provider is inherited, add a provider API key when prompted.

## 2. Register the cluster

In the workspace, select **Connect Cluster** and configure:

| Setting            | Minimum choice                                                                                                                                 |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| Cluster name       | A recognizable name such as `payments-prod`.                                                                                                   |
| Include namespaces | Add only the namespaces AcornOps should observe. Leave empty to use every namespace allowed by Kubernetes RBAC.                                |
| Exclude namespaces | Leave empty unless a namespace must be omitted.                                                                                                |
| Agent access       | Start with **Read-only**. Choose **Read-write** only when AcornOps should perform approved remediation and the cluster may receive write RBAC. |

Select **Continue to Install Agent**.

## 3. Install AgentK

Copy the complete generated Helm command. Confirm that `kubectl` points to the intended cluster, then run the command from an operator terminal.

Do not copy only part of the command: it contains the registration key, access mode, and namespace scope selected above.

Return to the management console and wait for **Agent connected**, then select **Done**.

## 4. Start a chat

Open the connected cluster, select **Chat Assistant**, and prompt it with a focused question such as:

> What needs attention on this cluster?