Choose a tested starting configuration for longhorn/longhorn@1.11.2. Read its exact Kubernetes objects, required setup, and current evidence before you deploy it.
Start with default. The page also shows other recorded choices. The page does not claim every possible values combination.
Evidence labels: Pass has a linked result. Watch names a limit to check. Blocked means do not use that path yet.
Upstream: the Catalog fetched chart longhorn from the Helm repository https://charts.longhorn.io at version 1.11.2. find this chart on Artifact Hub · Helm documentation. This page adds checked configurations and test results.
Every chart page follows the same order. Choose a configuration, inspect its objects and setup work, then read the tests that have run. Open the worked examples.
The page names the work and says which delivery path has actually run.
What To Use
default configuration: 41 rendered objects · 7 images · 0 target prerequisites · 0 hook or setup steps · 6/6 checks passing. These counts come from the linked test records.
defaultRecommended first base variant
2Supported base variants
Recommended first pathFirst-configuration status
Ready for a target-specific production reviewProduction status
Use the public catalog entry, then check the exact configuration and its tests before making a production claim.
No specific missing capability is recorded. The first configuration still needs review.
Namespace
longhorn-system
Four Separate Questions
Inspecting a source, producing objects, checking a destination, and checking a live result are different jobs. A Catalog match is useful for comparison but is not required. A missing destination or deployment is shown as not run or blocked, not as a failed configuration.
Question
Current answer
What it needs
Status
What do I have?
Inspect the helm source, choices, locks, and any existing output before selecting a destination.
Destination access: no Selected configuration deployed: no
Available to inspect evidence recorded
What will it produce?
Run the recorded Helm render step to produce the exact Kubernetes objects for this configuration.
Destination access: no Selected configuration deployed: no
Checked: passed evidence recorded
Can this destination accept it?
The destination has not been checked for this exact configuration. A recorded source or render result is not a destination pass.
Destination access: yes Selected configuration deployed: no
Not run no run recorded
Did it work?
No post-deployment result is recorded for this exact configuration. Publication, upload, or rendering is not proof that it ran correctly.
None in the catalog base. Later edits appear in ConfigHub Unit revision history or a derived variant.
No separate work is recorded; read the prerequisite and lifecycle status before assuming none is needed.
Upgrade rule: if a new Helm render and a ConfigHub revision both change the same field, review the overlap before promotion. The values profile shows the Helm side; Unit revision history shows the ConfigHub side.
Shipping a chart as plain rendered YAML is faster and simpler, and it silently drops anything Helm was going to do afterwards. This section reports what a scan of the packaged chart found, across 37 files.
Construct
Found
Why it matters when a chart ships as plain YAML
Helm hooks
3
Hook Jobs never fire, or fire under a different hook dialect.
Cluster lookups
1
The chart reads the cluster while rendering, so a render without one is valid but wrong.
Capability branching
1
The chart chooses apiVersions from the cluster it renders against.
Custom resource definitions
22
Per-file delivery can race the definitions the resources depend on.
A flattening-safety verdict has decided this version: default:unsafe-to-flatten; ui-ingress:unsafe-to-flatten. The verdict records one disposition per construct and names any companion artifact a flattened bundle must ship. What the flattening verdict means.
A construct being present does not make a chart unflattenable. Most are switched on or off by values, and a verdict records which ones the base you choose actually reaches. Read the catalog-wide evidence for how common each one is.
What The Starting Configuration Records
A base variant is a starting configuration we have already rendered and checked. Pick the one whose trade-off you want; the table below shows what each one changes. How the values for each are chosen.
The default base-variant record connects those Helm inputs to the Kubernetes objects, remaining requirements, hooks, CRDs, checks, and OCI status. Open it when you need the complete starting record rather than only the rendered YAML.
Open the full rendered YAML to read the actual manifest output. The render record and setup section explain the inputs, tests, CRDs, hooks, and other work around it.
If new Helm values create a useful starting configuration, record another base variant with its own inputs and checks. If one environment changes a field after rendering, record that change in a ConfigHub variant.
The exact installer package for this chart version. The version tag is readable, and the manifest digest makes a published pull immutable. Public catalog package refs are published in Google Artifact Registry with anonymous read access. No ConfigHub account or Google registry login is needed for the local setup path.
Required before apply
None recorded for the recommended base variant. No separate setup command recorded.
External resources the recommended base variant expects, such as an existing Secret, namespace, CRD, or target fact.
Instructions and decisions for hooks, CRDs, generated Secrets, setup jobs, cluster requirements, or blockers.
Choose base variant
Pick the supported Helm configuration for this chart: default, no-CRDs, existing Secret, HA, server-only, or another listed option.
Record inputs
Keep the values, namespace, release name, source lock, default render intent, full YAML output, package base, test results, and setup instructions together.
Handle chart extras
CRDs, hooks, setup jobs, external Secrets, target facts, and webhook certificates are recorded as chart-specific choices. Some are included in a base variant, some need a setup step, and some are blocked until there is a safe path.
Start with default. If a card says review or preparation is needed, treat that as a real limit rather than a ready install.
Package image
Exact package:oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/longhorn-longhorn:1.11.2@sha256:0617a692620540d997f515cba0ffc86c9cccd3b2b254d0a56698667cfc957b7f publication receipt recorded · open the exact publication receipt
Readable version tag: oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/longhorn-longhorn:1.11.2. The package is pinned so a republished tag cannot change what you get. The command below uses the exact manifest digest, so cub installer refuses different package bytes.
cub installer pull 'oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/longhorn-longhorn:1.11.2@sha256:0617a692620540d997f515cba0ffc86c9cccd3b2b254d0a56698667cfc957b7f' --work-dir ./package-review
less ./package-review/package/records/README.md
The package's records/ directory connects every base to its source choices, Helm render intent, Kubernetes objects, prerequisites, lifecycle work, and checks. These are supporting records, not Kubernetes objects.
Verify the package publisher
Run this command with cosign. It checks the expected publisher, the exact manifest digest, and the package annotations.
A valid signature identifies who signed these package bytes. It does not show that the configuration is suitable for your cluster; use this page's checks and setup instructions for that decision.
Public catalog package refs are published in Google Artifact Registry with anonymous read access. No ConfigHub account or Google registry login is needed for the local setup path.
Run the whole sequence as one script, prerequisites included: try.sh renders and applies to Kubernetes without an account; confighub.sh renders and uploads to your ConfigHub Space.
Before you run try.sh: it changes your current kubectl context. It runs the named prerequisites and applies the rendered objects. Read it first and use a disposable test cluster. confighub.sh does not apply anything to Kubernetes.
You should see something like this
Here is what the command does. cub installer is an open-source plugin for the cub CLI. cub installer setup pulls a catalog package and writes its Kubernetes files locally, leaving delivery to kubectl, Argo CD or Flux. The generated scripts stop before doing any work when the plugin or kustomize is missing.
cub installer setup ...
rendered manifests written under <work-dir>
use the chart option cards below to check pass, watch, blocked, and prerequisites
Current status: Available in the catalog · Reason: Promotion was tested and recorded in ConfigHub.
Use this entry in ConfigHub
Every Catalog entry page carries these five steps in this order. Each step says what the Catalog has run for this entry, and a step with a missing precondition gives no command.
Steps 1 and 2 need no account. Install the cub CLI before any cub command. Step 2 uses cub config diff, which cub plugin install confighub/cub-workshop@v0.6.61 adds. This page covers 2 entries, so open the one you want. A live walk on 2026-10-08 ran steps 3 to 5 for bitnami-nginx-24-0-2-http-clusterip and nvidia-gpu-operator-v26-3-3-default. These commands carry the changes that walk needed. It is a dated log and no receipt, so no state on this page rests on it.
Helm chart, base default, version 1.11.2What is fixed, and what you supply
Fixed when this entry was built. These went into the build, so the objects already carry them. To change one, build the entry again from its source.
chart is longhorn/longhorn
version is 1.11.2
base is default
valuesProfile is recipes/longhorn/longhorn/1.11.2/effective-values.yaml
namespace is longhorn-system
releaseName is longhorn
capabilityProfile is {"apiVersions":[],"kubeVersion":"1.30.0"}
Yours to supply or check. The listing records no input for the destination. The Catalog has not ruled one out for your cluster.
This entry's plan, and how to test it
The record lists no plan step for this entry.
Test the install steps yourself.This script carries them out with kubectl on a cluster you choose, with no account. Read it first and use a throwaway cluster. The Catalog has no recorded run of this script.
Compared with plain Helm. The Catalog installed this base beside plain Helm on two local clusters, and the two matched. Read the receipt.
The Catalog rendered this entry and retains its 41 objects in one file.
An upload can create more Units than the objects counted here. The installer renders a Namespace, and the upload adds an installer-record Unit.
# fetch the retained objects for this entry$ curl -fsSL -o longhorn-longhorn-1-11-2-default.yaml https://raw.githubusercontent.com/confighub/helm-expt/main/recipes/longhorn/longhorn/1.11.2/revisions/default/r001/rendered/release-objects.yaml
# check the bytes against the listing$ shasum -a 256 longhorn-longhorn-1-11-2-default.yaml
4a2f739775a696f5d67db6adf1f99473c60a3f5adf308ceb3ccbf222435acd90 longhorn-longhorn-1-11-2-default.yaml
# render this base from the signed package; step 3 uploads this directory$ cub installer setup --pull oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/longhorn-longhorn:1.11.2@sha256:0617a692620540d997f515cba0ffc86c9cccd3b2b254d0a56698667cfc957b7f --base default --work-dir ./longhorn-longhorn-1-11-2-default --non-interactive --namespace longhorn-system
2. Compare with another version or base Not run for this entry
The listing records no comparison for this entry. The commands run on the retained files, with no account. This version has one other base in the Catalog, ui-ingress. The Catalog holds 2 other versions, 1.12.0 and 1.12.1.
# fetch the ui-ingress base of the same version$ curl -fsSL -o longhorn-longhorn-1-11-2-ui-ingress.yaml https://raw.githubusercontent.com/confighub/helm-expt/main/recipes/longhorn/longhorn/1.11.2/revisions/ui-ingress/r001/rendered/release-objects.yaml
# list what differs between the two bases$ cub config diff longhorn-longhorn-1-11-2-default.yaml longhorn-longhorn-1-11-2-ui-ingress.yaml --summary
# fetch the default base at version 1.12.0$ curl -fsSL -o longhorn-longhorn-1-12-0-default.yaml https://raw.githubusercontent.com/confighub/helm-expt/main/recipes/longhorn/longhorn/1.12.0/revisions/default/r001/rendered/release-objects.yaml
# list what changes from 1.11.2 to 1.12.0$ cub config diff longhorn-longhorn-1-11-2-default.yaml longhorn-longhorn-1-12-0-default.yaml --summary
Replace each value in angle brackets with a name of your own. The entry id may already exist as a Space in your organization, and the package name as a Component.
In the live walk, a Space named for the nginx entry's id and a Component named bitnami-nginx already existed, so the walk chose its own names. The --component flag sets the Component label the upload writes on the Space, which is the package name when you omit it.
The cub installer plugin reads your organization from CUB_CONTEXT and ignores --context. If you use a context other than your default, export CUB_CONTEXT first, or the plugin works in your default organization.
# sign in; steps 3 to 5 write to your ConfigHub organization$ cub auth login
# upload step 1's directory as a Space of Units, under names you choose$ cub installer upload --work-dir ./longhorn-longhorn-1-11-2-default --space <your-space> --component <your-component>
# list the Units the upload created$ cub unit list --space <your-space>
4. Deploy it Not run for this entry
No delivery run is recorded for this entry. Argo CD has not run, Flux has not run, and kubectl has not run. The commands name the Target workshop/target, which cub cluster up --name workshop creates on a local kind cluster with Argo CD. Use your own Target for a real destination. The coverage lanes record a local Kubernetes run and a GitOps OCI run for this base. They are separate from the delivery record this step reads. Read the log of the live walk on 2026-10-08.
Use the Space name you chose in step 3. The delete command is needed because the cloned installer-record Unit carries the Target and Argo CD v3.5.4 cannot read it, a defect seen on cub v0.8.7 and server v0.8.9.
Without that line the walk deployed nothing and Argo CD showed Unknown, while every cub command exited 0. The walk ran the four commands in this order and did not try them without the first publish.
ConfigHub shows nothing when Argo CD fails to read a Release. Run kubectl -n argocd get applications.argoproj.io and read the Sync column, because Healthy alone is not a pass. Argo CD took between 18 seconds and about 5 minutes to read a Release on a cluster made without argobot.
The walk made its cluster with cub cluster up --no-argobot. That command creates two Spaces, a Worker, a Target and a Trigger, opens ports 30010 to 30019 on the machine, and installs Argo CD from an unpinned upstream manifest.
Removing the ConfigHub side does not remove the workload. In the walk, deleting the Application Unit and the Spaces left the Application and its pods running, because the root Application does not prune.
# clone the base onto a Target as a dev variant$ cub variant create dev <your-space> --target workshop/target --space-pattern "template:<your-space>-dev"
# publish the Release that the cluster's Argo CD pulls$ cub release publish <your-space>-dev
# delete the installer record, which Argo CD cannot read$ cub unit delete --space <your-space>-dev installer-record
# publish again without it$ cub release publish <your-space>-dev
5. Promote a change Partly run for this entry
A promotion ran for this entry. It ran the preview and the promote. The delete and the publish below have no recorded run for this entry. Promotion carries a change in the base to the dev variant. The base changes when you edit a Unit or upload a newer version into the same Space. Read the log of the live walk on 2026-10-08 · Read the record that states this.
The promotion changes the dev Space and publishes nothing. It also adds the installer-record Unit back with the Target. The change reaches the cluster only after the delete and the publish.
The preview lists the whole installer record as added. In the walk, the preview of a one-label change to gpu-operator ran to 405 lines, and about 400 of them were that record.
# preview what the dev variant would take from the base$ cub variant promote <your-space>-dev --dry-run -o mutations
# promote once you have read the preview$ cub variant promote <your-space>-dev --change-desc "Pull the reviewed base forward"
# delete the installer record that the promotion adds back$ cub unit delete --space <your-space>-dev installer-record
# publish the Release that carries the change$ cub release publish <your-space>-dev
Helm chart, base ui-ingress, version 1.11.2What is fixed, and what you supply
Fixed when this entry was built. These went into the build, so the objects already carry them. To change one, build the entry again from its source.
chart is longhorn/longhorn
version is 1.11.2
base is ui-ingress
valuesProfile is recipes/longhorn/longhorn/1.11.2/effective-values-ui-ingress.yaml
namespace is longhorn-system
releaseName is longhorn
capabilityProfile is {"apiVersions":[],"kubeVersion":"1.30.0"}
Yours to supply or check. The listing records no input for the destination. The Catalog has not ruled one out for your cluster.
This entry's plan, and how to test it
The record lists no plan step for this entry.
Test the install steps yourself.This script carries them out with kubectl on a cluster you choose, with no account. Read it first and use a throwaway cluster. The Catalog has no recorded run of this script.
Compared with plain Helm. The Catalog installed this base beside plain Helm on two local clusters, and the two matched. Read the receipt.
The Catalog rendered this entry and retains its 42 objects in one file.
An upload can create more Units than the objects counted here. The installer renders a Namespace, and the upload adds an installer-record Unit.
# fetch the retained objects for this entry$ curl -fsSL -o longhorn-longhorn-1-11-2-ui-ingress.yaml https://raw.githubusercontent.com/confighub/helm-expt/main/recipes/longhorn/longhorn/1.11.2/revisions/ui-ingress/r001/rendered/release-objects.yaml
# check the bytes against the listing$ shasum -a 256 longhorn-longhorn-1-11-2-ui-ingress.yaml
2f6508c2bc3f2a09e1ffcb8ec71282b3e2dd52e69fe8ca80fc90ab756f9b9298 longhorn-longhorn-1-11-2-ui-ingress.yaml
# render this base from the signed package; step 3 uploads this directory$ cub installer setup --pull oci://europe-west1-docker.pkg.dev/nth-fort-499605-q5/helm-expt/longhorn-longhorn:1.11.2@sha256:0617a692620540d997f515cba0ffc86c9cccd3b2b254d0a56698667cfc957b7f --base ui-ingress --work-dir ./longhorn-longhorn-1-11-2-ui-ingress --non-interactive --namespace longhorn-system
2. Compare with another version or base Not run for this entry
The listing records no comparison for this entry. The commands run on the retained files, with no account. This version has one other base in the Catalog, default. The Catalog holds 2 other versions, 1.12.0 and 1.12.1.
# fetch the default base of the same version$ curl -fsSL -o longhorn-longhorn-1-11-2-default.yaml https://raw.githubusercontent.com/confighub/helm-expt/main/recipes/longhorn/longhorn/1.11.2/revisions/default/r001/rendered/release-objects.yaml
# list what differs between the two bases$ cub config diff longhorn-longhorn-1-11-2-ui-ingress.yaml longhorn-longhorn-1-11-2-default.yaml --summary
# fetch the default base at version 1.12.0$ curl -fsSL -o longhorn-longhorn-1-12-0-default.yaml https://raw.githubusercontent.com/confighub/helm-expt/main/recipes/longhorn/longhorn/1.12.0/revisions/default/r001/rendered/release-objects.yaml
# list what changes from 1.11.2 to 1.12.0$ cub config diff longhorn-longhorn-1-11-2-ui-ingress.yaml longhorn-longhorn-1-12-0-default.yaml --summary
Replace each value in angle brackets with a name of your own. The entry id may already exist as a Space in your organization, and the package name as a Component.
In the live walk, a Space named for the nginx entry's id and a Component named bitnami-nginx already existed, so the walk chose its own names. The --component flag sets the Component label the upload writes on the Space, which is the package name when you omit it.
The cub installer plugin reads your organization from CUB_CONTEXT and ignores --context. If you use a context other than your default, export CUB_CONTEXT first, or the plugin works in your default organization.
# sign in; steps 3 to 5 write to your ConfigHub organization$ cub auth login
# upload step 1's directory as a Space of Units, under names you choose$ cub installer upload --work-dir ./longhorn-longhorn-1-11-2-ui-ingress --space <your-space> --component <your-component>
# list the Units the upload created$ cub unit list --space <your-space>
4. Deploy it Not run for this entry
No delivery run is recorded for this entry. Argo CD has not run, Flux has not run, and kubectl has not run. The commands name the Target workshop/target, which cub cluster up --name workshop creates on a local kind cluster with Argo CD. Use your own Target for a real destination. The coverage lanes record a local Kubernetes run and a GitOps OCI run for this base. They are separate from the delivery record this step reads. Read the log of the live walk on 2026-10-08.
Use the Space name you chose in step 3. The delete command is needed because the cloned installer-record Unit carries the Target and Argo CD v3.5.4 cannot read it, a defect seen on cub v0.8.7 and server v0.8.9.
Without that line the walk deployed nothing and Argo CD showed Unknown, while every cub command exited 0. The walk ran the four commands in this order and did not try them without the first publish.
ConfigHub shows nothing when Argo CD fails to read a Release. Run kubectl -n argocd get applications.argoproj.io and read the Sync column, because Healthy alone is not a pass. Argo CD took between 18 seconds and about 5 minutes to read a Release on a cluster made without argobot.
The walk made its cluster with cub cluster up --no-argobot. That command creates two Spaces, a Worker, a Target and a Trigger, opens ports 30010 to 30019 on the machine, and installs Argo CD from an unpinned upstream manifest.
Removing the ConfigHub side does not remove the workload. In the walk, deleting the Application Unit and the Spaces left the Application and its pods running, because the root Application does not prune.
# clone the base onto a Target as a dev variant$ cub variant create dev <your-space> --target workshop/target --space-pattern "template:<your-space>-dev"
# publish the Release that the cluster's Argo CD pulls$ cub release publish <your-space>-dev
# delete the installer record, which Argo CD cannot read$ cub unit delete --space <your-space>-dev installer-record
# publish again without it$ cub release publish <your-space>-dev
5. Promote a change Partly run for this entry
A promotion ran for this entry. It ran the preview and the promote. The delete and the publish below have no recorded run for this entry. Promotion carries a change in the base to the dev variant. The base changes when you edit a Unit or upload a newer version into the same Space. Read the log of the live walk on 2026-10-08 · Read the record that states this.
The promotion changes the dev Space and publishes nothing. It also adds the installer-record Unit back with the Target. The change reaches the cluster only after the delete and the publish.
The preview lists the whole installer record as added. In the walk, the preview of a one-label change to gpu-operator ran to 405 lines, and about 400 of them were that record.
# preview what the dev variant would take from the base$ cub variant promote <your-space>-dev --dry-run -o mutations
# promote once you have read the preview$ cub variant promote <your-space>-dev --change-desc "Pull the reviewed base forward"
# delete the installer record that the promotion adds back$ cub unit delete --space <your-space>-dev installer-record
# publish the Release that carries the change$ cub release publish <your-space>-dev
After You Render It
The first command writes files and does not apply them. Read the objects and setup requirements, then choose the next job.
cub plugin install confighub/homebrew-tap@cub-scan-v0.7.3 --name scan cub check --format json --output cub-check.json <work-dir>/out/manifests. The check is advisory and does not apply anything.
Apply the rendered manifests with kubectl, or publish reviewed objects as OCI
Each card is one available way to use this chart in the catalog. Some cards are runnable base variants. Others are candidate paths, derived variants, or review notes that explain what still has to be prepared.
Checks: Each card names what was checked and says whether it passed, needs review, was blocked, was not run, or was not needed.
try.sh renders, settles the prerequisites in order, and applies with kubectl; confighub.sh renders and uploads to your ConfigHub Space.
Evidence
Live helm vs confighub parity
Hooks/actions
No separate hook or action for this row.
Who runs actions?
No separate action runner for this row.
Lifecycle record
The current review found no separate hook or setup step for this base. Open the full record.
Prerequisites
The support review found no separate target prerequisite for the supported default base for the recorded cub-lk-kind-vanilla test target in namespace longhorn-system, delivered from ConfigHub OCI through Argo CD. Evidence: Support decision · Target evidence.
Next
Choose the target ready base; Then record explicit security acceptance or create a hardened base before claiming a target run path
Reason
Promotion was tested and recorded in ConfigHub.
Helm outputPassedSaved in ConfigHubPassedLocal clusterPassedSetup stepNot neededGitOps and OCIPassedLive Helm comparisonPassedTwo clustersPassedPromotionPassed
try.sh renders, settles the prerequisites in order, and applies with kubectl; confighub.sh renders and uploads to your ConfigHub Space.
Evidence
Live helm vs confighub parity
Hooks/actions
No separate hook or action for this row.
Who runs actions?
No separate action runner for this row.
Lifecycle record
The current review found no separate hook or setup step for this base. Open the full record.
Prerequisites
This base has not yet been reviewed for required Secrets, CRDs, namespaces, values, storage services, external APIs, or target topology. Record what it needs, or record that nothing extra is required.
Next
Choose the target ready base; Then record explicit security acceptance or create a hardened base before claiming a target run path
Reason
Promotion was tested and recorded in ConfigHub.
Helm outputPassedSaved in ConfigHubPassedLocal clusterPassedSetup stepNot neededGitOps and OCIPassedLive Helm comparisonPassedTwo clustersPassedPromotionPassed
We ran cub check v0.7.3 against the exact rendered objects for every configuration below. The result is advisory: read each finding and decide whether it matters for your target.
25 advisory findings 6 critical, 17 warning, 2 info Container does not set runAsNonRoot Container does not disable allowPrivilegeEscalation DaemonSet container does not set runAsNonRoot
27 advisory findings 7 critical, 18 warning, 2 info Container does not set runAsNonRoot Container does not disable allowPrivilegeEscalation IngressClass not found when Ingress specifies ingressClassName
What this does not check: hook execution, CRD readiness, target Secrets and cloud services, admission behavior, workload health, or rollback. The linked Catalog review covers chart-specific source and operating questions. ConfigHub validation and approval are separate managed controls.
Every reference below comes from the reviewed rendered output. What you see is what the cluster pulls. These references are data: you can change a registry or pin a digest with a recorded edit, and prove the change landed in every environment.
Base variant
Images
default
description: Share manager image used for creating a share manager description: The support bundle manager image docker.io/longhornio/longhorn-manager:v1.11.2 docker.io/longhornio/longhorn-share-manager:v1.11.2 docker.io/longhornio/longhorn-ui:v1.11.2 minLength: 1 type: string
ui-ingress
description: Share manager image used for creating a share manager description: The support bundle manager image docker.io/longhornio/longhorn-manager:v1.11.2 docker.io/longhornio/longhorn-share-manager:v1.11.2 docker.io/longhornio/longhorn-ui:v1.11.2 minLength: 1 type: string
First-Run Caveats
Some chart paths need a small preparation step before the cub path feels as smooth as Helm. We show those steps here so the first run does not surprise you.
Caveat
What to do
Universal caveats
Use declared inputs or bases instead of Helm --set. For direct delivery, define pruning and field-conflict behavior. Use Argo CD or Flux when that controller path and its pruning settings are recorded for the selected preset.
Shared placeholder password
No shared placeholder password caveat recorded for this chart.
CRD first-ordering
Yes. 25 CRD object(s) are recorded. Follow the base's recorded plan: apply CRDs first and wait, use a controller-specific ordering rule, or choose the separable CRD base when one is available.
Did this version string point at changed upstream bytes?
Not checked
No linked result
How much is proven, and what more testing would add: Fully proven: Render parity, ConfigHub proof, Local live, GitOps/OCI live, Live Helm-vs-ConfigHub, Two-cluster kind.
Base
Readiness
Render
ConfigHub
Local live
GitOps/OCI
Live parity
Two-cluster kind
default
start-here
pass
pass
pass
pass
pass
pass
ui-ingress
start-here
pass
pass
pass
pass
pass
pass
What We Tested On A Cluster
This is the result of a real run for one base variant on one recorded target setup. It does not silently extend the result to other bases or clusters.
Question
Recorded answer
Base variant
ui-ingress
Target used
cub-managed kind proof cluster with target profile kind-ingress-nginx
Observed result
pass
What passed
regular Helm deployment path reached the harness-defined runtime state ConfigHub direct-apply leg reached the harness-defined runtime state ConfigHub OCI/Argo leg reached the harness-defined workload runtime state Helm-vs-ConfigHub semantic parity passed for the OCI/Argo leg Argo CD reported the application Synced Argo CD reported the application Healthy Longhorn manager, driver deployer, engine image, UI, and CSI workloads became ready in the chart's longhorn-system namespace Longhorn UI Ingress was rendered and applied with host longhorn.example.test and ingressClassName nginx Longhorn UI Ingress received status.loadBalancer.ingress=localhost
What the result means
The previous watch row was target-fit, not parity. When the proof target includes the kind-ingress-nginx profile, the UI Ingress receives a localhost address and Argo reports Healthy.
What this does not prove
This row does not prove external UI reachability through a production ingress controller. This row does not prove production storage safety, backup/restore, replica placement, disk scheduling, or upgrade policy. This row does not prove Longhorn can be safely installed into arbitrary namespaces.
exact rendered objects with render parity and receipts; cluster lookups lifted into declared target facts
Field
Value
Known quirks
Required values; Generated facts.; Tpl; Rbac
You must provide
target facts at variant time; mandatory chart inputs
What ConfigHub records
exact rendered objects with render parity and receipts; cluster lookups lifted into declared target facts
Optional chart inputs
None identified in the chart facts
How optional inputs are handled
No handling rule is recorded
Hooks, CRDs, And Setup Work
Some Helm charts need work before, during, or after apply: CRDs, hooks, setup jobs, webhook certificates, migrations, generated Secrets, or checks. For each chart, the catalog should make the choice clear: include it in the base variant, split it into a separate base variant, run a setup step, use a GitOps action where evidence exists, require an existing target resource, or block it when there is no safe default.
If no plan is shown, that does not prove the upstream chart has no hooks. It means the public catalog has no chart-specific action to show yet; check the matrix or send a problem chart if hook behavior should be modeled. Direct apply, Argo CD, Flux, and upgrade implementations are tracked separately. One passing implementation does not prove the others.
Modeled action area
Current status
Checks and policies already reviewed
CRD lifecycle and upgrade policy; cluster RBAC review; hook and setup order; warning review and apply-gate policy; webhook readiness and failure policy
Why this lifecycle status is shown
The recipe records no separate Helm hook that needs its own action.
A green render or local live result is not a production support claim. Production support is target-scoped and uses the support-decision artifact when present.
CRD lifecycle and upgrade policy; cluster RBAC review; hook and setup order; warning review and apply-gate policy; webhook readiness and failure policy
Open policy decisions
None recorded for this policy checklist
Next action
Keep the target-scoped evidence fresh before using this supported scope as a production-support example; create separate backup/restore, upgrade, replica-policy, storage-class, UI-ingress, resource-hardened, or digest-pinned bases for real customer Longhorn workloads.