apiVersion: helm-expt.confighub.com/v1alpha1
kind: HelmCatalogDemoReadme
metadata:
  name: readme
  labels:
    app.kubernetes.io/part-of: helm-catalog
    helm-expt.confighub.com/space: "byo-nginx-ai-values-24-0-2-staging"
    helm-expt.confighub.com/readme-kind: "environment"
spec:
  space: "byo-nginx-ai-values-24-0-2-staging"
  title: "Promote the NGINX change to staging"
  summary: "A staging variant that received the reviewed four-replica change from development."
  sourcePath: "data/helm-catalog-readmes/spaces/byo-nginx-ai-values-24-0-2-staging/README.md"
  links:
    - label: "Original values review"
      url: "https://github.com/confighub/helm-expt/blob/main/data/byo-helm-values-review/summary.md"
    - label: "First deployment result"
      url: "https://github.com/confighub/helm-expt/blob/main/data/byo-helm-values-deploy-proof/summary.md"
    - label: "Development-to-staging promotion"
      url: "https://github.com/confighub/helm-expt/blob/main/data/byo-helm-values-promotion-proof/summary.md"
    - label: "Promoted staging deployment"
      url: "https://github.com/confighub/helm-expt/blob/main/data/byo-helm-values-staging-deploy-proof/summary.md"
    - label: "NGINX chart page"
      url: "https://confighub.github.io/helm-expt/site/charts/bitnami-nginx-24-0-2.html"
  markdown: |-
    <!-- Generated by npm run helm-catalog-readmes. Do not edit by hand. -->

    # Promote the NGINX change to staging

    A staging variant that received the reviewed four-replica change from development.

    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 values files between environments makes it hard to prove what moved and what stayed local.

    This Space shows one concrete promotion: a tested field change moves from development to staging, while ConfigHub keeps the relationship and revision history.

    ## What this example shows

    - Staging started as a three-replica copy of development in its own namespace.
    - Development changed to four replicas while staging stayed at three.
    - The promotion updated staging to four replicas without changing the saved base or losing the staging namespace.
    - The staging Unit records its upstream link and the exact promoted revision.

    ## Where each setting comes from

    | Place | What this Space records |
    | --- | --- |
    | Starting configuration | Staging began from the reviewed three-replica NGINX configuration and keeps its own namespace. |
    | ConfigHub changes | The promotion records the development change to `spec.replicas: 4` while retaining the staging namespace. Revision history identifies both sources. |
    | Install work | The existing Secret requirement remains inherited from the reviewed base. |
    | Live cluster | A throwaway Argo CD run observed four ready replicas after promotion. That observation checks the promoted setting; it does not create it. |

    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 configuration Unit to see the four-replica staging result.
    - Revision history to see the `UpgradeUnit` promotion record.
    - `byo-nginx-ai-values-24-0-2-development` for the upstream change.

    ## Evidence and source

    - [Original values review](https://github.com/confighub/helm-expt/blob/main/data/byo-helm-values-review/summary.md)
    - [First deployment result](https://github.com/confighub/helm-expt/blob/main/data/byo-helm-values-deploy-proof/summary.md)
    - [Development-to-staging promotion](https://github.com/confighub/helm-expt/blob/main/data/byo-helm-values-promotion-proof/summary.md)
    - [Promoted staging deployment](https://github.com/confighub/helm-expt/blob/main/data/byo-helm-values-staging-deploy-proof/summary.md)
    - [NGINX chart page](https://confighub.github.io/helm-expt/site/charts/bitnami-nginx-24-0-2.html)

    ## Limits

    - The promotion dry-run did not print a useful mutation preview. The command left stored data unchanged, but the empty output remains a product limitation.
    - The promoted staging result reached four ready replicas through Argo CD on one throwaway kind cluster. It has not been tested on a long-lived or production target.