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

# Kubernetes

> Deploy self-hosted Runlayer on your EKS or GKE cluster using the Runlayer Operator

The Runlayer Operator installs and reconciles the Runlayer application on an **EKS or GKE cluster you provision and operate**. It manages `RunlayerInstance` platform workloads and `MCPServer` deployments. You supply the cluster, database, cache, cloud resources, identity, DNS, and ingress.

## Deployment path

1. Collect [Runlayer-provided inputs](/deployment/runlayer-provided-inputs) and review [egress requirements](/deployment/egress-requirements).
2. Prepare the cluster using [Kubernetes prerequisites](/deployment/kubernetes-prerequisites).
3. Provision [external dependencies](/deployment/external-dependencies), including PostgreSQL and Redis.
4. Configure [workload identity](/deployment/workload-identity) and the permissions needed by your selected features.
5. Follow the [Operator deployment guide](/deployment/runlayer-operator) to install the operator, create namespaces and Secrets, deploy a `RunlayerInstance`, configure ingress, and verify readiness.

Choose optional components before provisioning their dependencies. The deployment guide covers [optional components](/deployment/runlayer-operator#optional-components-snippet) and [Kubernetes agent sandboxes](/deployment/runlayer-operator#k8s-agent-sandbox-sandboxmode-k8s).

Use [Updates](/operations/updates) for subsequent releases and rollback. The legacy [EKS Terraform guide](/deployment/eks-terraform) is deprecated and should not be used for new installations.

For AWS without Kubernetes, see [ECS + Terraform](/deployment/ecs).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.