chore(chart): Bump chart to v2.8.0 for CSI driver release v0.14.0 - #253
Merged
Merged
Conversation
Bump the chart to 2.8.0 and appVersion to 0.14.0, and align the sidecar
tags with deploy/k8s, closing the drift that built up while the chart
waited on a release to bump against:
- csi-provisioner v6.1.1 => v6.2.1
- csi-attacher v4.10.0 => v4.12.0
- csi-resizer v2.0.0 => v2.2.1
- csi-node-driver-registrar v2.15.0 => v2.17.0
- livenessprobe v2.17.0 => v2.19.0
Also correct the controller and node image tag comments. They claimed the
default was v{{ .Chart.AppVersion }}, but the templates use
.Chart.AppVersion without a v prefix, which is correct: the release
workflow strips the leading v before pushing, so images are published as
0.14.0 rather than v0.14.0.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue #, if available: n/a
Description of changes:
Bumps the chart to
2.8.0/appVersion: 0.14.0now that driver release v0.14.0 is tagged, and aligns the sidecar tags withdeploy/k8s. This closes the drift that had built up since 989566c, which updated only the raw manifests because the chart could not be bumped without a release to bump against.deploy/k8s)Merging this lets
chart-releaserpublish the chart, which it has not done since 2.7.0.One change beyond the version bump
The controller and node image tag comments (
values.yaml:139,245) claimed the default wasv{{ .Chart.AppVersion }}. The templates actually use.Chart.AppVersionwith novprefix, and that is correct:.github/workflows/release.yaml:53strips the leadingv(sed -e 's/^v//') before pushing, so images are published as0.14.0, notv0.14.0. The comments were the only thing wrong, and left as-is they invite someone to "fix" the template and break the default image reference. Happy to drop this from the PR if you would rather keep the diff to the version bump alone.Testing performed:
helm lint charts/cloudstack-csi— passes (only the pre-existing "icon is recommended" note).deploy/k8s/*.yaml— empty diff, confirming the chart and manifests now agree exactly.ghcr.io/leaseweb/cloudstack-csi-driver:0.14.0andghcr.io/leaseweb/cloudstack-csi-sc-syncer:0.14.0, matching the tags the release workflow publishes for thev0.14.0tag.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
🤖 Generated with Claude Code