1. Take an entry into a stack or into ConfigHub
Open the chart page and follow its first command. Inspect the generated objects and required setup before you decide where they should run.
Choosing several components for a platform? Build a small Kubara platform from tested Catalog entries, or compose a stack from certified parts. Upload a published entry into ConfigHub to release, promote, and govern it, or deploy it directly with the reconciler you already run.
Is my configuration right? · Try it: Redis in ten minutes · Run it with Flux, Argo CD, or kubectl · Use with your AI · Worked examples
2. Continue from the retained answer
Start with the public Promote my config comparison. ConfigHub is the next step when the same proposed object hash must move through named environments with approvals, release digests, and target results.
| Job | What ConfigHub keeps | Start here |
|---|---|---|
| Compare development and production | Both variants, their source relationship, and exact object diff. | Compare environments |
| Promote and publish | The reviewed change, approval, promotion result, and immutable release OCI. | Promotion and OCI examples |
| Roll back | The prior object revision or release digest. External effects remain outside the rollback claim. | Redis promotion and rollback |
| Compare desired with live | The approved desired objects and a separately dated live observation. | Desired and live comparison |
| Roll out to a fleet | The selected targets, waves, approvals, and result for every target. | Fleet examples |