apiVersion: helm-expt.confighub.com/v1alpha1
kind: HelmCatalogDemoReadme
metadata:
  name: readme
  labels:
    app.kubernetes.io/part-of: helm-catalog
    helm-expt.confighub.com/space: "aicr-eks-h100-training-kubeflow-v0-14-0-argocd-staging"
    helm-expt.confighub.com/readme-kind: "environment"
spec:
  space: "aicr-eks-h100-training-kubeflow-v0-14-0-argocd-staging"
  title: "Promote the AICR change to staging"
  summary: "This staging variant received the reviewed Grafana existing-Secret change from development while keeping the other 16 AICR Applications unchanged."
  sourcePath: "data/helm-catalog-readmes/spaces/aicr-eks-h100-training-kubeflow-v0-14-0-argocd-staging/README.md"
  links:
    - label: "AICR example guide"
      url: "https://github.com/confighub/helm-expt/blob/main/docs/demo/aicr/eks-h100-training-kubeflow.md"
    - label: "Public OCI receipt"
      url: "https://github.com/confighub/helm-expt/blob/main/examples/aicr/eks-h100-training-kubeflow/public-oci-receipt.yaml"
    - label: "Development and staging promotion"
      url: "https://github.com/confighub/helm-expt/blob/main/examples/aicr/eks-h100-training-kubeflow/promotion-readiness-receipt.yaml"
    - label: "Required-approval check"
      url: "https://github.com/confighub/helm-expt/blob/main/examples/aicr/eks-h100-training-kubeflow/apply-policy-receipt.yaml"
  markdown: |-
    <!-- Generated by npm run helm-catalog-readmes. Do not edit by hand. -->

    # Promote the AICR change to staging

    This staging variant received the reviewed Grafana existing-Secret change from development while keeping the other 16 AICR Applications unchanged.

    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

    Copying a large generated platform bundle into staging would hide the one intended difference.

    This Space records the upstream relationship and proves that the promotion changed only the reviewed kube-prometheus-stack Application.

    ## What this example shows

    - Staging started from the same 17-Application baseline as development.
    - The promotion preview reported one changed Unit and left staging unchanged.
    - The completed promotion made staging match the reviewed development configuration.
    - Required approval and the other catalog checks remain attached before any apply.

    ## 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-kubeflow` Unit to inspect the promoted result.
    - The Unit revision history to see the ConfigHub promotion.
    - `aicr-eks-h100-training-kubeflow-v0-14-0-argocd-development` for the upstream review.

    ## Evidence and source

    - [AICR example guide](https://github.com/confighub/helm-expt/blob/main/docs/demo/aicr/eks-h100-training-kubeflow.md)
    - [Public OCI receipt](https://github.com/confighub/helm-expt/blob/main/examples/aicr/eks-h100-training-kubeflow/public-oci-receipt.yaml)
    - [Development and staging promotion](https://github.com/confighub/helm-expt/blob/main/examples/aicr/eks-h100-training-kubeflow/promotion-readiness-receipt.yaml)
    - [Required-approval check](https://github.com/confighub/helm-expt/blob/main/examples/aicr/eks-h100-training-kubeflow/apply-policy-receipt.yaml)

    ## Limits

    - The target must provide `monitoring/aicr-grafana-admin` before delivery.
    - The promotion proves stored configuration and policy behavior. It does not prove Argo CD reconciliation or GPU workload health.