This Space exists to answer one practical question: what is a safe, repeatable way to run ingress-nginx/ingress-nginx@4.15.1 for this operating choice?
For this Space, the answer is the default preset. Use this when you want to start from the chart author's normal path, with the inputs recorded.
The preset keeps the upstream Helm chart. The catalog records the chart version, values, namespace, release name, Kubernetes capabilities, source lock, rendered YAML, and evidence, so the team can repeat this choice later.
Why this preset exists
With plain Helm, a values file and a successful install do not explain enough later. It can be hard to tell which values, Secrets, CRDs, hooks, target assumptions, and local edits mattered. A future upgrade can also wipe changes made after install.
This preset gives the team a named starting point instead of a private guess. You can test it without a ConfigHub account, upload it when you want Hub records and variants, and reuse it as a base for dev, staging, production, regions, or customers.
What this preset contains
- Preset:
default. - Kubernetes YAML: 11 object(s), mainly Service x2, ClusterRole x1, ClusterRoleBinding x1, ConfigMap x1, Deployment x1, IngressClass x1, Role x1, RoleBinding x1.
- Needs before install: 1 Secret.
- Extra Helm work: no hook route is recorded for this preset.
This is not a new chart language. It is a checked way to use this Helm chart, with the chosen inputs and output kept together.
Where each setting comes from
There are four places to look. The public preset itself contains no ConfigHub edits: it is the recorded Helm render that later ConfigHub variants start from.
| Place | What this Space records | Where to change it |
|---|---|---|
| Helm values | The values profile defines the default base together with release ingress-nginx and namespace ingress-nginx. | Change the values and create or update a base preset when Helm needs to produce different objects. |
| ConfigHub changes | None in this catalog base. After upload, an edit appears in Unit revision history or in a derived environment variant. | Edit the rendered object in ConfigHub when the base shape is right but a field needs to differ for an environment, region, customer, or policy. |
| Install work | 1 Secret; no separate hook or setup route is recorded. | Follow the prerequisite and route records. Secrets, CRDs, and setup jobs are not hidden as values or ConfigHub edits. |
| Live cluster | Live state is checked against the reviewed configuration; it does not become the desired setting by itself. | Record an intended fix in ConfigHub, or remove an unintended live change as drift. |
If a later Helm render and a ConfigHub revision both change the same field, review that overlap before promotion. Do not let two layers silently own one setting.
What to inspect in Hub
- Read this page first.
- Open the
recipeUnit for the chart version and setting-source record, then follow its values-profile path to see what Helm was given. - Open the Kubernetes YAML to see what Helm produced.
- Open Unit revision history to see any later ConfigHub change.
- Open routes or prerequisites when the chart needs CRDs, hooks, Secrets, setup jobs, or target facts.
Try it
Run without a ConfigHub account:
bash <(curl -fsSL https://confighub.github.io/helm-expt/site/sh/ingress-nginx-ingress-nginx-4-15-1/default/try.sh)Upload to ConfigHub:
bash <(curl -fsSL https://confighub.github.io/helm-expt/site/sh/ingress-nginx-ingress-nginx-4-15-1/default/confighub.sh)Evidence and source
| Item | Link |
|---|---|
| Catalog chart page | ingress-nginx/ingress-nginx@4.15.1 |
| Helm values profile | recipes/ingress-nginx/ingress-nginx/4.15.1/effective-values.yaml |
| Render intent | data/helm-render-intents/intents/ingress-nginx-ingress-nginx-4-15-1-default.yaml |
| Rendered YAML | recipes/ingress-nginx/ingress-nginx/4.15.1/revisions/default/r001/rendered/release-objects.yaml |
| Detailed guide | data/confighub-example-guides/spaces/ingress-nginx-ingress-nginx-4-15-1-default/README.md |
| No-account script | try.sh |
| ConfigHub upload script | confighub.sh |
What is proven
- Render parity:
yes. - Local kind run:
yes. - GitOps OCI live run:
yes. - Live Helm versus ConfigHub comparison:
yes.
These claims apply to this preset. They do not mean every possible values combination for the chart has been tested.
Limits
- This README covers this recorded preset, not every possible values file.
- No hook route is recorded for this preset.