This example records the Kube Prometheus Stack install order and the tested 85.3.3 to 86.1.0 no-crds upgrade through Argo CD and Flux.
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
A successful Helm render is not a complete install plan for this chart. Kubernetes must see the CRDs first, and the admission webhook needs certificate setup and readiness checks.
We keep the upstream chart, make each step visible beside the rendered objects, and retain a receipt for the path that ran.
What this example shows
- The package carries ten checked CRDs, so they can be applied and established before the chart's custom resources.
- Eight route Units record the CRD order, webhook setup, upgrade jobs, checks, target facts, and cleanup behavior.
- Seven fresh-install steps passed in the direct script, using the chart's own certificate and webhook patch Jobs.
- Argo CD and Flux installed 85.3.3, upgraded to 86.1.0, replaced both completed setup Jobs, and passed the runtime checks.
- The top-level routes stay
automatic: falsebecause ConfigHub does not yet select this chart-specific plan for the user.
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 eight LifecycleRoute Units.
- The Kube Prometheus Stack chart page and render intent.
Evidence and source
- Hooks and CRDs guide
- Kube Prometheus Stack chart page
- Direct lifecycle proof
- Argo CD and Flux upgrade proof
- CRD ordering proof
- Lifecycle receipt
- Render intent
Limits
- The direct receipt covers a fresh install; the controller receipt covers the exact no-crds 85.3.3 to 86.1.0 version pair.
- Rollback, long-running soak, and automatic post-success removal of every temporary hook resource have not run.
- ConfigHub stores and checks the route records but does not yet choose and execute all eight routes automatically.