grafana/grafana 10.5.15 - existing-secret-ingress

This guide explains the journey from a public Helm chart to a ConfigHub Space. Use it when you want to know why this preset exists, what problem it solves, how to repeat it, and what still needs care.

It is generated from the same records that build the package, chart page, render intent, scripts, and receipts. The proof links are lower down.

Why this preset exists

Helm charts often expose many settings, but a values file alone does not tell the whole operations story. A team still needs to know what Kubernetes objects will be created, which Secrets or CRDs must already exist, whether hooks or setup jobs need special handling, and what evidence backs the result.

This preset is a named answer for one useful operating choice. It keeps the upstream chart, records the inputs and rendered YAML, and gives the team a repeatable starting point instead of a private values-file guess.

What this is

This is the existing-secret-ingress preset config for grafana/grafana@10.5.15. The repo also calls this a base variant. Use this when secret material should come from a Secret you create, not from a generated chart default.

The matching catalog page is grafana/grafana@10.5.15.

The chart journey

We keep the Helm chart. We lock grafana/grafana@10.5.15, choose the existing-secret-ingress preset config, render it with the recorded values, namespace, release name, and Kubernetes capabilities, then save the output as files.

That captured output is the render variant: recipes/grafana/grafana/10.5.15/revisions/existing-secret-ingress/r001/rendered/release-objects.yaml. It contains 9 Kubernetes object(s): ClusterRole x1, ClusterRoleBinding x1, ConfigMap x1, Deployment x1, Ingress x1, Role x1, RoleBinding x1, Service x1.

The public package is oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/grafana-grafana:10.5.15. Users can pull it without cloning this repo. When someone runs cub installer upload, ConfigHub stores the rendered Kubernetes YAML in a Space so it can be searched, compared, reviewed, changed, and delivered. The example script defaults to Space helm-grafana-existing-secret-ingress, but users can choose another name with CUB_SPACE=....

What to check

This preset config records 1 prerequisite: 1 Secret. Follow the instructions below before you apply the rendered objects.

The catalog does not currently record a separate hook, setup job, or cleanup step for this preset.

Secret material is kept outside the chart render and supplied by you. At least one Secret must be created with your values before apply.

Why you can trust it

• The chart version, source, namespace, release name, values, and capability profile are recorded in the render intent.
• The render variant is committed as YAML and contains 9 Kubernetes object(s).
• The installer package OCI ref points to the package users pull for this chart version.
• Render parity is recorded as passing for this preset config.
• Prerequisites are named before apply, so they are not discovered after rollout.

This is a claim about this recorded preset config. It is not a claim that every possible values file for this chart has been checked.

Repeat it

Fast path with no ConfigHub account:

bash <(curl -fsSL https://confighub.github.io/helm-expt/site/sh/grafana-grafana-10-5-15/existing-secret-ingress/try.sh)

Fast path with a ConfigHub account:

bash <(curl -fsSL https://confighub.github.io/helm-expt/site/sh/grafana-grafana-10-5-15/existing-secret-ingress/confighub.sh)

The core render command is:

New to cub? Install the cub CLI first. You can pull and render public catalog packages without an account. Commands that save or change ConfigHub data require you to sign in.

What this command does. cub installer is a released, open-source plugin for the cub CLI. cub installer setup pulls a catalog package and writes its Kubernetes files locally. It does not apply those files to a cluster; use kubectl, Argo CD, or Flux for delivery. The generated scripts stop before doing any work when the plugin or kustomize is missing.

cub installer setup --pull oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/grafana-grafana:10.5.15 --base existing-secret-ingress --work-dir ./grafana-grafana-10-5-15-existing-secret-ingress --non-interactive --namespace grafana

After upload, create environment versions with cub variant create and move reviewed changes with cub variant promote. The walkthrough is After Upload: Create A Variant And Promote Changes.

Preset details

Prerequisites and lifecycle steps

Evidence

Limits

• Production support is target-scoped. Use production support decisions before claiming production readiness.

Source files

• Chart page: https://confighub.github.io/helm-expt/site/charts/grafana-grafana-10-5-15.html
• Render intent: data/helm-render-intents/intents/grafana-grafana-10-5-15-existing-secret-ingress.yaml
• Rendered YAML: recipes/grafana/grafana/10.5.15/revisions/existing-secret-ingress/r001/rendered/release-objects.yaml
• Package source: packages/grafana/grafana/10.5.15/bases/existing-secret-ingress
• Generated scripts: site/sh/grafana-grafana-10-5-15/existing-secret-ingress
• Preset doctrine: Helm Chart Presets And Values