A landing space for the demo org. Start with the chart and demo spaces instead of treating this as a chart example.
Start here when you open this Space in Hub. This page explains the problem this example is meant to show, what to inspect, why it matters, and where the evidence lives.
Why this example exists
The demo org is easier to understand when every Space explains what it is for.
This README prevents a first-time user from landing in an empty or administrative place and thinking the demo is thin.
What this example shows
- ConfigHub always has a default Space, so the demo org has one too.
- It is not the main Helm Catalog demo. Use it as orientation, then open one of the named chart, fleet, route, or environment spaces.
Where each setting comes from
| Place | What this Space records |
|---|---|
| Starting configuration | Open the upstream Space or source link named on this page. That is the configuration this Space started from. |
| ConfigHub changes | Open Unit revision history. It records changes made after the starting configuration was saved. |
| Install work | Use the linked chart or route evidence for required Secrets, CRDs, hooks, setup jobs, and target facts. |
| Live cluster | Use target observations to compare the cluster with the reviewed Units. A live-only edit is drift until it is recorded or removed. |
If an upstream change and a local ConfigHub revision touch the same field, review the overlap before promotion.
What to inspect in Hub
- This README first.
platformfor the shared checks used by the demo org.- Any chart preset Space whose name starts with a chart name.
Evidence and source
Limits
- This is not a chart recipe, a rendered app, or a production example.