Installation & Setup
This section covers everything you need to deploy OpenBox on your infrastructure — 4 install scenarios, the Helm chart reference, and customization patterns.
Match your team to a scenario
Answer 2 questions to land on the right install path:
Scenarios at a glance
| Scenario | Who deploys | Where | Best fit |
|---|---|---|---|
| S1 Turnkey Managed | Openbox team | Fresh AWS (customer account) | Enterprise with no DevOps team; wants SLA |
| S2 Fresh AWS Self-Service | Your DevOps team | Fresh AWS | Mature DevOps; wants full control (Terraform + CloudFormation both supported) |
| S3 Bring Your Own Cluster | Your DevOps team | Existing EKS / AKS / GKE / self-managed K8s | Already have K8s platform |
| S8 Local PoC | You (dev) | Laptop (Minikube/kind) | Sales demo, developer eval |
S5 Hybrid Managed
Documented as a variant of S1 (Openbox provisions, then handoff to customer). Not a separate scenario page in the MVP — contact sales for the hybrid handoff timeline.
Deferred scenarios
Not covered in the MVP docs — file a request if you need one of these:
- S4 Air-gapped — cluster with no internet (banking, gov, defense)
- S6 Non-AWS clouds — Azure AKS, GCP GKE, OCI
- S7 On-prem / bare metal — Rancher / OpenShift / Kubespray on physical hardware
The Helm chart itself is cloud-agnostic, but the step-by-step docs currently focus on AWS + local. Non-AWS mappings are documented in Architecture → AWS integration surface.
Read next
Before installing:
- System requirements → — hardware, storage, GPU, network sizing per scenario
After picking a scenario:
- Follow the scenario's step-by-step guide
- Reference Helm chart basics → for
values.yamlreference - Apply Customization → patterns for common overrides