Skip to main content
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 and review egress requirements.
  2. Prepare the cluster using Kubernetes prerequisites.
  3. Provision external dependencies, including PostgreSQL and Redis.
  4. Configure workload identity and the permissions needed by your selected features.
  5. Follow the Operator deployment guide 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 and Kubernetes agent sandboxes. Use Updates for subsequent releases and rollback. The legacy EKS Terraform guide is deprecated and should not be used for new installations. For AWS without Kubernetes, see ECS + Terraform.