Installation
1. Install the bops-env CLI
The easiest path, once any version of bops-env is on your machine, is letting it fetch itself:
bops-env self install # fetches and installs the latest release
bops-env self uninstall # removes a self-installed binary
That's only available on Linux (the only platform with a published binary today) and needs a bops-env already on PATH to bootstrap from — for the first install, or for Windows/macOS, grab a signed prebuilt binary directly:
# Linux amd64
curl -LO https://github.com/blanketops/environments-cli/releases/latest/download/bops-env-static
chmod +x bops-env-static
sudo mv bops-env-static /usr/local/bin/bops-env
# Linux arm64
curl -LO https://github.com/blanketops/environments-cli/releases/latest/download/bops-env-static-arm64
chmod +x bops-env-static-arm64
sudo mv bops-env-static-arm64 /usr/local/bin/bops-env
Verify the download before running it — every release is signed with cosign (keyless) and carries a SLSA provenance attestation:
# Verify the signature (fetch the matching .sig asset first)
curl -LO https://github.com/blanketops/environments-cli/releases/latest/download/bops-env-static.sig
cosign verify-blob --certificate-identity-regexp ".*" --signature bops-env-static.sig bops-env-static
# Verify the attestation via GitHub CLI
gh attest verify bops-env-static --owner blanketops
Or build it locally from source (the only path today on Windows and macOS, which have no published binary yet):
git clone https://github.com/blanketops/environments-cli.git
cd environments-cli
mage install # builds and installs to ~/.local/bin (falls back to ~/bin; %USERPROFILE%\.local\bin on Windows)
Confirm it's on your PATH:
bops-env version
Run it with no arguments and bops-env prints its banner, the cluster context it's connected to, and a full command reference.
2. Point at a Cluster
If you already have a Kubernetes cluster and a working kubectl context, skip to step 3.
Otherwise, spin up a local Kind cluster:
bops-env cluster up dev
Useful companions:
bops-env cluster status dev # is it up?
bops-env cluster down dev # tear it down
3. Install the Operator
bops-env install
This applies the CRDs, RBAC, and controller-manager Deployment published by environments-install — every resource in the chain:
| Group | Resources |
|---|---|
environments.blanketops.dev | Environment, Build, Package, ServiceUnit, Deployment |
sources.blanketops.dev | GitRepository |
events.blanketops.dev | GitHubEvent |
networks.blanketops.dev | Route, Domain |
4. Install the Platform Stack
The operator reconciles BlanketOps Environments CRDs into workloads on a supporting stack: carvel, argoevents, tekton-pipelines, tekton-dashboard, shipwright, crossplane, externalsecrets, buildstrategies, flux, knative, and kourier. Install the whole stack in one shot:
bops-env dependencies install
This can take several minutes on a fresh cluster — it's pulling and starting every component in the stack.
Each dependency is also individually addressable, useful when you only need to reinstall one piece:
bops-env dependencies list # every dependency name above
bops-env dependencies status # install status for all of them
bops-env dependencies status knative # status for just one
bops-env dependencies install knative # (re)install just one
bops-env dependencies uninstall knative # remove just one
5. Confirm It's Running
bops-env dependencies status
Or check pods directly:
kubectl get pods -A
Look for Running pods across the blanketops-environments, kapp-controller, argo-events, tekton-pipelines, shipwright-build, crossplane-system, external-secrets, flux-system, knative-serving, and kourier-system namespaces before moving on. buildstrategies has no namespace of its own — it registers cluster-scoped ClusterBuildStrategy resources instead, so bops-env dependencies status buildstrategies is how you check it.
Uninstalling
In reverse order:
bops-env dependencies uninstall
bops-env uninstall
bops-env cluster down dev # only if you created a Kind cluster in step 2
Continue to Quickstart.