| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Chart 0.20.1 carries the corrected image defaults: the Apache-based cassandra build 5.0.8-nv-2.0.1 (the previous default tag was never published) and migrations 0.16.0. Consume it in the self-managed stack. The stack must also point the cassandra image at the renamed "cassandra" repository for the new default to resolve; that rename is in review separately. Signed-off-by: along <along@nvidia.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 2e73e308-ab3c-4e91-b141-1a6fe386e441 📥 CommitsReviewing files that changed from the base of the PR and between 02b46d5 and ecc411f. 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 12 included reviews per hour; 10 remain after this review. 📝 Walkthrough WalkthroughThe self-managed deployment updates the Cassandra chart to 0.20.1. It also changes the initialization image repository to cassandra and supports an optional configured image tag. ChangesCassandra deployment update
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to ecc41 The PR updates the self-managed Cassandra chart and image defaults so installs use the published Apache-based image while preserving tag overrides; no actionable merge-blocking risk remains after normal checks and review. Possibly related PRs
Suggested reviewers: rohithb-hub, sparve-nv 🚥 Pre-merge checks | ✅ 5 ✅ Passed checks (5 passed)
Comment @coderabbitai help to get the list of available commands. |
Sorry, something went wrong.
The Apache-based chart publishes its image as "cassandra"; the retired "bitnami-cassandra" repository has no 5.0.8 builds. Add a tag knob following the migrations pattern so environments can override the chart default. Drop the dynamicSeedDiscovery image block: the chart has no such key, so the values were dead. Signed-off-by: along <along@nvidia.com>
| Back | FazBrowse Home | New Git URL |
Why
Chart helm-nvcf-cassandra 0.20.1 was published with the corrected image
defaults (cassandra 5.0.8-nv-2.0.1; the previous default tag was never
published under the Apache image name). The self-managed stack still
pins 0.19.1 and still points the image at the retired
"bitnami-cassandra" repository, so cassandra installs from main cannot
pull the image.
What changed
cassandra release chart version 0.19.1 to 0.20.1.
image at the renamed "cassandra" repository and add a tag knob
following the migrations pattern; drop the dynamicSeedDiscovery image
block, which the chart has no key for (dead Bitnami-era values).
Customer Release Notes
Self-hosted: cassandra installs pull the published Apache-based image
by default; environments can still override the tag.
Plan Summary
Cassandra release in the self-managed stack: chart 0.19.1 to 0.20.1,
image repository "bitnami-cassandra" to "cassandra". Image defaults
move to cassandra 5.0.8-nv-2.0.1 and migrations 0.16.0.
Usage
Not applicable
Testing
emits the renamed image at the published tag for both the cassandra
container and the cassandra-conf-init initContainer.
chart defaults alone resolve the same tag.
Notes
Overlaps with the CLI install-path PR, which carries the same
global.yaml.gotmpl rename for the BDD suite: after this merges, that
branch needs a rebase that drops its duplicate hunk, and the
cassandra.image.tag pins in its BDD fixtures become redundant.
References
Relates to #1019
Summary by CodeRabbit