Starting examples
Choose one row. You do not need to understand the rest of the catalog first.
| What you have | What the example does | Start and proof | ConfigHub and OCI |
|---|---|---|---|
| A ready-made Helm package | Pull Redis, render one preset configuration, inspect its objects, and check the recorded Helm parity and install requirements. | Short example · Full walkthrough · GitHub source | Public installer OCI. Open its reference and package details. ConfigHub Space guide |
| Your own Helm chart and values | Render the supplied chart and values without applying them. The worked review keeps the intended replica change and fixes six risky or weaker settings. | Worked NGINX example · GitHub source · Review and proof | Public literal configuration OCI; exact reference is in the publication record. ConfigHub Space guide |
| An AICR recipe or bundle | The AICR example publishes a source OCI and a 17-Application literal OCI, imports the literal objects into ConfigHub, and promotes one reviewed change from development to staging. | Walkthrough · GitHub source · Round-trip proof | Public source OCI plus public literal configuration OCI; digests are in the publication receipt. ConfigHub Space guide |
| An existing OCI package | Inspect its exact objects or change one named field, then pull the result back and compare it with the reviewed files. | Inspect OCI · Change OCI · GitHub source · Proof | Permanent public OCI: oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/nginx-replicas-4@sha256:aa58e2a9d120d09f029fdef80596225f8c44d0aa629b18766fe8b6694659f518.Publication and exact import proof · ConfigHub Space guide |
| Kubernetes YAML or an existing app | Upload four ordinary Kubernetes files without running Helm or another renderer. Read the four ConfigHub Units back and compare them with the source. | Existing-app guide · GitHub fixture · Exact import proof | ConfigHub Space guide. The focused receipt stops after import; the official tutorial continues into change, release, production, and promotion. |
Where a starting example can run
| Choice | Available now? | What it means |
|---|---|---|
| Local or CI | Yes | No ConfigHub Server and no ConfigHub account. Public package pulls also need no Google registry login. |
| Hosted without sign-in | Planned | A public service will inspect open configuration without creating private history, variants, approvals, or releases. |
| ConfigHub | Yes | Save the reviewed objects, then follow the official tutorial. An account is required. |
These three choices apply to starting examples. The examples below use ConfigHub Server because their job is to manage saved configuration.
Continue in ConfigHub
| Job | Working example | Where to go |
|---|---|---|
| Save and change | Upload reviewed objects as a base variant. Make an exact development or customer change without changing the source chart. | Variants · Command walkthrough |
| Promote | Redis and NGINX examples record derived changes, promote them in order, publish reviewed OCI artifacts, and check the resulting workloads. | BYO Helm promotion · Redis promotion and rollback |
| Deliver through OCI | NGINX and the hook fixture have passed recorded OCI delivery through Argo CD, Flux, and direct apply without rerendering the reviewed objects. | Delivery guide · Argo CD and Flux proof |
| Apply checks and approvals | Schema, placeholder, and lifecycle-route checks can block bad configuration. Image and probe checks warn. Selected production and system configuration also requires approval. | Functional proof · Policy assignments |
Platform and fleet examples
| Example | What has run | Open |
|---|---|---|
| Kubara | One approved Kubara configuration passed its recorded route work, OCI delivery, Argo CD bootstrap, and a healthy Metrics Server result on one cluster. | Walkthrough · GitHub source · Proof · Space guide |
| Sveltos | A reviewed ClusterProfile moved from one pilot cluster to two staging clusters at a second OCI digest, and Sveltos restored a deliberately drifted value. | Walkthrough · GitHub source · Proof · Space guide |
ConfigHub App examples
Each row has a working, bounded example. The final column says what is still missing from a general product capability.
| App | Working example | Open | Still to build |
|---|---|---|---|
| Upgrade App | Redis upgrades from chart 25.5.3 to 27.0.0 without losing a post-render replica change, moves through development and staging, reaches two Argo CD clusters, and rolls back. | Walkthrough · GitHub source · Proof · Space guide | This is a guarded demonstration and receipt, not a finished ConfigHub App interface. |
| Hooks and CRDs App | Kube Prometheus Stack passes the recorded CRD, certificate, workload, webhook, and runtime sequence on fresh installs and on an 85.3.3 to 86.1.0 upgrade through Argo CD and Flux. | Walkthrough · GitHub source · Proof · Space guide | ConfigHub does not yet select and execute the chart-specific route automatically. |
| RBAC Review App | One review removes unnecessary Secret access, keeps ConfigMap access, requires approval, publishes OCI, and reaches Kubernetes through Argo CD. | Walkthrough · GitHub source · Proof · no permanent demo Space | The example does not yet build a complete RBAC binding graph across a live fleet. |
| Fleet Platform App | Kubara proves one platform target, while Sveltos proves a pilot and two-cluster expansion with separate reviewed OCI digests and drift recovery. | Walkthrough · GitHub source · Proof · Space guide | A large mixed-source fleet rollout with failure-based pausing remains open. |
| AI Change Review App | The example finds an unpinned image and inline API key, clears the reviewed replacement, and proves that approval controls the ConfigHub apply dry-run. | Walkthrough · GitHub source · Proof · no permanent demo Space | Kubernetes delivery, promotion, rollback, GPU workload health, and live observation have not run for this candidate. |
Where the material lives
| Place | What belongs there |
|---|---|
| This website | Short explanations, starting points, chart pages, worked examples, and links to current proof. |
| GitHub | Source configuration, generators, scripts, checks, receipts, and every file used to make the website. |
| The ConfigHub helm-catalog organization | Persistent demo Spaces. Each Space has one README Unit that explains its purpose and the Units it contains. Open the demo-org guide. |
| Public OCI registry | Stable starting packages and reviewed public outputs. Each permanent artifact must have a role, digest, source record, human guide, and publication receipt. |
| ConfigHub release OCI | Approved outputs from managed Spaces for Argo CD, Flux, or another recorded delivery path. |
| Temporary proof registry | Short-lived artifacts used by a receipt. The site must not advertise them as permanent packages. |
Open the detailed entry-path reference for commands, artifact distinctions, source-to-OCI automation, hooks, CRDs, and the full set of proof links.