A development variant that changes the reviewed NGINX result from three replicas to four without changing the saved base.
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 useful reviewed configuration soon needs a development version. The important part is that the team can change the real Kubernetes object without editing or forking the Helm chart.
This Space records that change and keeps the checked base available for comparison.
What this example shows
- The reviewed base remains the exact three-replica result imported from the public OCI package.
- Development has its own namespace and changes the Deployment directly to four replicas.
- The container image stays pinned, the existing-Secret reference stays in place, and the reviewed security settings stay unchanged.
- The catalog checks are inherited from the base.
Where each setting comes from
| Place | What this Space records |
|---|---|
| Starting configuration | The upstream link points to the reviewed three-replica NGINX base imported from OCI. |
| ConfigHub changes | Development changes the Deployment directly to spec.replicas: 4 and records that edit in Unit revision history. The Helm values file is not changed or rerun. |
| Install work | The existing Secret requirement stays inherited from the reviewed base. |
| Live cluster | This development Space has not been used as a long-lived target. Its four-replica value is desired configuration, not a runtime observation. |
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 and its revision history to see the replica change.
byo-nginx-ai-values-24-0-2-reviewedfor the unchanged upstream base.byo-nginx-ai-values-24-0-2-stagingfor the promoted result.
Evidence and source
- Original values review
- First deployment result
- Development-to-staging promotion
- Promoted staging deployment
- NGINX chart page
Limits
- Four replicas are a demonstration choice, not a sizing recommendation.
- This development Space has not been deployed to a long-lived cluster.