Kubara generated the Helm source and cluster values for a small Kubernetes platform. ConfigHub stores the exact rendered objects as one reviewed base variant.
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
Kubara can choose a platform stack and generate its source configuration. The operations problem starts after that: teams need to review the exact result, compare cluster versions, and move a tested change through a fleet.
Kubara still generates the platform. ConfigHub gives the team one place to review the result, compare cluster versions, approve changes, and see what each cluster should run.
What this example shows
- Kubara v0.12.0 selected and configured Argo CD, cert-manager, External Secrets, Prometheus, Metrics Server, Traefik, and a small portal.
- The recorded render contains 77 Kubernetes objects. ConfigHub stores the 75 non-Secret objects; the two Secrets remain named requirements instead of being hidden.
- The route record lists three CRDs, four Helm-hook resources, the two Secrets, and the External Secrets prerequisite.
- This Space requires approval before apply because it changes cluster-wide platform configuration.
- A live test ran the required CRD, Secret, and Redis setup work, delivered a portable OCI through Argo CD, and brought up one selected Metrics Server Application.
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.
- The
release-objectsUnit to inspect the Kubernetes objects Kubara produced. - The route record in the evidence links to see what must happen around normal apply.
Evidence and source
- Kubara example guide
- Generation receipt
- ConfigHub upload receipt
- CRD, hook, Secret, and prerequisite record
- OCI delivery and live result
- Apply policy and live assignments
Limits
- The portable OCI used a temporary registry; no permanent public Kubara package is claimed.
- The live test selected Metrics Server only. It deferred the ClusterExternalSecret and gRPC Ingress because their target prerequisites were absent.
- The full seven-service profile and a multi-cluster promotion wave have not run.