apiVersion: helm-expt.confighub.com/v1alpha1
kind: HelmCatalogDemoReadme
metadata:
  name: readme
  labels:
    app.kubernetes.io/part-of: helm-catalog
    helm-expt.confighub.com/space: "bitnami-nginx-fleet-prod-us"
    helm-expt.confighub.com/readme-kind: "fleet"
spec:
  space: "bitnami-nginx-fleet-prod-us"
  title: "Nginx fleet prod-us"
  summary: "One lane in the Nginx fleet demo, showing how a chart-based app can vary by environment or region."
  sourcePath: "data/helm-catalog-readmes/spaces/bitnami-nginx-fleet-prod-us/README.md"
  links:
    - label: "Nginx chart page"
      url: "https://confighub.github.io/helm-expt/site/charts/bitnami-nginx-24-0-2.html"
    - label: "Org exhibit summary"
      url: "https://github.com/confighub/helm-expt/blob/main/data/helm-org/exhibits.csv"
  markdown: |-
    <!-- Generated by npm run helm-catalog-readmes. Do not edit by hand. -->

    # Nginx fleet prod-us

    One lane in the Nginx fleet demo, showing how a chart-based app can vary by environment or region.

    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

    The fleet demo is about scale. Once one chart becomes dev, staging, production, regions, or customers, values files and manual notes become hard to trust.

    ConfigHub keeps each lane named and inspectable while preserving the shared base.

    ## What this example shows

    - A chart can become several named application versions without forking the chart.
    - Different lanes can receive base changes at different times.
    - This lane shows the normal path for carrying a reviewed base change forward.

    ## 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.
    - Nginx Deployment and Service YAML.
    - Sibling fleet Spaces to compare the lanes.

    ## Evidence and source

    - [Nginx chart page](https://confighub.github.io/helm-expt/site/charts/bitnami-nginx-24-0-2.html)
    - [Org exhibit summary](https://github.com/confighub/helm-expt/blob/main/data/helm-org/exhibits.csv)

    ## Limits

    - The demo proves the shape of a fleet workflow. It is not a full production rollout policy.