Describe what should be investigated or refactored
The examples/longhorn package is pinned to Longhorn v1.4.0 (released
December 2022). Upstream is currently at v1.11.1. The example no longer
reflects a version a user would realistically deploy and the pinned image
list / chart values have drifted significantly from the current chart.
Bump the example to the latest stable Longhorn release. Concretely:
metadata.version and charts[0].version → latest Longhorn chart versionlonghorn-environment-check file source URL + shasum → matching tag (is this stil accurate?)- Regenerate the
images: list to match the new chart's rendered manifests
(image set has changed between 1.4 and 1.11 — new sidecars, dropped
components)
- Refresh
values.yaml against the new chart defaults, preserving the
K3s-specific kubeletRootDir override that motivates the file
Links to any relevant code
Additional context
Validation should include creating the package against an offline cluster.
Describe what should be investigated or refactored
The
examples/longhornpackage is pinned to Longhornv1.4.0(releasedDecember 2022). Upstream is currently at
v1.11.1. The example no longerreflects a version a user would realistically deploy and the pinned image
list / chart values have drifted significantly from the current chart.
Bump the example to the latest stable Longhorn release. Concretely:
metadata.versionandcharts[0].version→ latest Longhorn chart versionlonghorn-environment-checkfile source URL + shasum → matching tag (is this stil accurate?)images:list to match the new chart's rendered manifests(image set has changed between 1.4 and 1.11 — new sidecars, dropped
components)
values.yamlagainst the new chart defaults, preserving theK3s-specific
kubeletRootDiroverride that motivates the fileLinks to any relevant code
Additional context
Validation should include creating the package against an offline cluster.