1. Where ConfigHub fits
Four verbs, one reviewed configuration
Release it by digest, promote it from development to production, gate a release on an approval, and roll back the configuration to exactly what ran.
Come here after the check
Come here after you have inspected the Kubernetes objects. They may have come from Helm, an AICR recipe for AI infrastructure, cub installer, OCI, or plain YAML.
Stop, publish, or upload
You can stop with local files, publish them directly as OCI, or upload them to ConfigHub and publish a reviewed release OCI later.
ConfigHub keeps the history
ConfigHub stores your approved configuration and its history. Use it when you need to track changes across environments, require an approval before production, or roll back to a recorded release. Start with what ConfigHub adds.
2. The same commands run from a free check to a governed release
Whatever a configuration started as, it takes the same steps. The first steps are free and need no account. The next need a ConfigHub account. The last is the commercial product.
| Verb | What it does | Command or surface |
|---|---|---|
| check | Inspect it: what it installs, whether it is right. No cluster. | the Check |
| deploy (a planned name, not yet a command) | Run the reviewed OCI on the Argo CD or Flux you already run. | cub installer, or your own kubectl, Flux, or Argo CD |
| upload | Bring it into ConfigHub as a base. Public config chains into your private org here. | cub variant upload |
| release | Publish an approved, immutable release with history, so the cluster pulls that instead of a hand-pushed bundle. | cub release publish |
| promote | Move a reviewed change from development to production. | cub variant promote |
| govern | Run a stack under governance: approvals, releases, rollback, drift, a fleet view. | the commercial product |
A stack adds free commands of its own, check and sandbox, and a fleet places one across many clusters. Those run today as a plugin prototype. See stacks and fleets.
Every source becomes exact Kubernetes objects and any required setup before it reaches this page. See what each format becomes, and see what happens to hooks, CRDs, and setup work.
3. Where to go next
Release, promote and roll back runs the four verbs. Operate a fleet takes them across many clusters. ConfigHub Server says what an account adds.