Spin Up a Local OpenFrame Platform on k3d With One Command

Setting up a Kubernetes platform locally usually means a few hours of yak-shaving: installing a cluster, wiring up ArgoCD, clicking through dashboards, and hoping nothing breaks along the way. If you've done it more than once, you know the drill. OpenFrame CLI is a tool that collapses that whole process into a single command, and it's worth a look if you work with Kubernetes on a regular basis.

What It Does

OpenFrame CLI (openframe) is an interactive command-line tool for provisioning Kubernetes clusters and deploying the OpenFrame platform onto them. It handles clusters in two flavors: locally via k3d (Kubernetes-in-Docker) or in the cloud via GKE and EKS, with Terraform doing the heavy lifting under the hood. Once a cluster exists, the CLI deploys OpenFrame using ArgoCD's app-of-apps pattern.

The tool manages the full lifecycle of an OpenFrame deployment — checking prerequisites, provisioning the cluster, installing the platform, monitoring status, upgrading, and tearing it all down. It's the primary bootstrap tool for OpenFrame, the AI-driven MSP platform built by Flamingo, though the main platform code lives in a separate repository (flamingo-stack/openframe-oss-tenant) that this CLI deploys and manages.

Every workflow supports both an interactive wizard with prompts, spinners, and cost estimates, and non-interactive flags (--non-interactive, --skip-wizard) for CI pipelines. So you can use it as a friendly guided setup on your laptop or as a scripted step in automation.

Why It's Cool

One command gets you a working platform. The headline feature is openframe bootstrap, which creates a local k3d cluster and installs the entire OpenFrame stack (ArgoCD plus app-of-apps) in a single step. That's the kind of thing that usually takes a README, a few Stack Overflow tabs, and an afternoon. Here it's one command.

Prerequisites management is built in. The CLI detects missing tools — Docker, k3d, Helm, Terraform, gcloud, AWS CLI — and can auto-install them on macOS and Linux. If you've ever spent twenty minutes figuring out which version of Helm you're supposed to have, this is a welcome change.

It's honest about security. All tool binaries are downloaded with pinned versions and SHA256 checksum verification, explicitly avoiding the curl | bash pattern that's become too common. CLI self-updates are verified with Sigstore/cosign signatures, and there's rollback support if an update goes sideways. That's a level of care you don't always see in bootstrap tools.

The status dashboard is a nice touch. openframe app status --interactive gives you a k9s-style terminal UI for inspecting ArgoCD application health and triggering syncs. If you spend a lot of time in the terminal, this fits right in.

Cluster provisioning is provider-agnostic. Local k3d for development, GKE or EKS for cloud — all through the same interface, all backed by Terraform. You don't have to relearn the tool when you move from your laptop to a real environment.

One thing to flag: the hardware requirements aren't trivial. You'll want at least 24 GB of RAM, 6 CPU cores, and 50 GB of disk for a full local install (32 GB, 12 cores, and 100 GB recommended). Running a full platform inside k3d on your machine is heavy, and the README is upfront about that. Cloud deployments shift most of the load to the provider, but your local host still needs enough room for Docker, Terraform, and Helm.

How to Try It

Getting started depends on your platform. On Windows, you can grab the AMD64 build directly from the releases page:

https://github.com/flamingo-stack/openframe-cli/releases/latest/download/openframe-cli_windows_amd64.zip

Unzip it and run the binary. For macOS and Linux, check the repository's install section — the README covers auto-install of prerequisites on those platforms.

Once installed, the main workflow is:

1. Run openframe bootstrap to create a local k3d cluster and deploy OpenFrame in one step.
2. Use openframe app status --interactive to watch ArgoCD application health in a live terminal UI.
3. When you're done, tear everything down through the CLI rather than manually cleaning up Docker containers and cluster resources.

For automation, add --non-interactive or --skip-wizard to any workflow, and the CLI will run without prompting.

The full source and documentation live at github.com/flamingo-stack/openframe-cli.

Final Thoughts

OpenFrame CLI is aimed at developers and platform engineers who need to stand up OpenFrame environments repeatedly — whether that's for local development, testing, or cloud deployments. The combination of a single-command bootstrap, built-in prerequisite handling, and a genuinely thoughtful approach to binary verification makes it a solid piece of tooling. The main caveat is the resource footprint: a full local install is not something you'll run on a lightly-specced laptop. But if your machine can handle it, the time savings over a manual setup are real. It's a good example of a bootstrap tool that treats the boring parts — checksums, rollbacks, prerequisite detection — as first-class features rather than afterthoughts.

Follow @githubprojects for more developer tools and open source projects.