This development variant starts with the 17 Applications produced by AICR and changes only the Grafana administrator setting in the kube-prometheus-stack Application.
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 generated platform bundle still needs target-specific choices. A password for Grafana should come from a Secret owned by the target, not remain as a literal value in the generated Application.
This Space makes that choice explicit without editing the AICR package or changing the other 16 Applications.
What this example shows
- The saved AICR base remains unchanged and records the public literal-configuration OCI digest.
- Development replaces the literal Grafana admin password with a reference to the
aicr-grafana-adminSecret. - The dry-run named one changed Application and left the stored configuration unchanged.
- The same six catalog checks remain attached, including required approval for system configuration.
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
aicr-eks-h100-training-kubeflowUnit to inspect all 17 Applications. - The Unit revision history to see the one-Application development change.
aicr-eks-h100-training-kubeflow-v0-14-0-argocdfor the unchanged public-OCI base.
Evidence and source
Limits
- The target must provide
monitoring/aicr-grafana-adminwith the expected user and password keys. - This development configuration has not been reconciled by Argo CD on an EKS GPU cluster.