feat(seaweedfs): bump chart to 4.34 - #2913
Conversation
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (9)
📝 WalkthroughWalkthroughSeaweedFS Helm chart bumped from v4.31 to v4.34. SFTP certificate-based authentication added for both standalone and all-in-one deployments, including a new CA Secret template. JWT token expiry is now configurable per signing mode. Two new Grafana panels visualize filer object size distribution. Bucket versioning ChangesSeaweedFS Chart v4.34 Updates
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 Trivy (0.69.3)Trivy execution failed: 2026-06-15T07:49:39Z FATAL Fatal error run error: fs scan error: scan error: scan failed: failed analysis: post analysis error: post analysis error: kubernetes scan error: fs filter error: fs filter error: walk error range error: stat smartylint.json: no such file or directory: range error: stat smartylint.json: no such file or directory Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
`@packages/system/seaweedfs/charts/seaweedfs/templates/sftp/sftp-ca-secret.yaml`:
- Around line 10-24: The template is incorrectly reading allInOne.sftp.* when
only allInOne.enabled is true; change each override guard that currently uses
.Values.allInOne.enabled to require both .Values.allInOne.enabled and
.Values.allInOne.sftp.enabled before copying any allInOne.sftp.* values
(specifically the overrides for $authMethods, $inlineCAKeys, and
$existingSecret), and also change the top-level conditional that decides to
render the CA secret to require .Values.allInOne.sftp.enabled in addition to
.Values.allInOne.enabled so generated secrets are only suppressed when the
all-in-one SFTP feature is explicitly enabled; apply the same gating logic
upstream and re-vendor here.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: b95af626-778d-47a3-a5ea-3696ec9c0ce0
📒 Files selected for processing (9)
packages/system/seaweedfs/charts/seaweedfs/Chart.yamlpackages/system/seaweedfs/charts/seaweedfs/dashboards/seaweedfs-grafana-dashboard.jsonpackages/system/seaweedfs/charts/seaweedfs/templates/all-in-one/all-in-one-deployment.yamlpackages/system/seaweedfs/charts/seaweedfs/templates/cert/ca-cert.yamlpackages/system/seaweedfs/charts/seaweedfs/templates/sftp/sftp-ca-secret.yamlpackages/system/seaweedfs/charts/seaweedfs/templates/sftp/sftp-deployment.yamlpackages/system/seaweedfs/charts/seaweedfs/templates/shared/post-install-bucket-hook.yamlpackages/system/seaweedfs/charts/seaweedfs/templates/volume/volume-resize-hook.yamlpackages/system/seaweedfs/charts/seaweedfs/values.yaml
💤 Files with no reviewable changes (2)
- packages/system/seaweedfs/charts/seaweedfs/templates/cert/ca-cert.yaml
- packages/system/seaweedfs/charts/seaweedfs/templates/volume/volume-resize-hook.yaml
|
Heads-up: this bump will keep failing E2E the same way #2834 already broke it on main — the failure is not flaky. Two regressions came with chart 4.31 and are still present in 4.33:
Both (1) and (2) reproduce with a plain |
Pulls in upstream SeaweedFS 4.34, which includes: - SIGHUP-based hot-reload of JWT signing keys (seaweedfs/seaweedfs#9826, fixing seaweedfs/seaweedfs#9823). Operators recovering from key rotation or mismatch no longer need to restart 'weed' processes — kill -HUP is enough. - Native 'expires_after_seconds' values for jwt.signing / jwt.signing.read / jwt.filer_signing / jwt.filer_signing.read, exposed under global.seaweedfs.securityConfig.jwtSigning.expiresAfterSeconds. This supersedes the patch in the now-closed cozystack#2911. 'make update' driven; patches in 'patches/' reapplied cleanly. Signed-off-by: IvanHunters <xorokhotnikov@gmail.com>
d634f11 to
c692a16
Compare
|
Superseded by #2918 (rebased on cleaner branch name |
Summary
Pulls in upstream SeaweedFS 4.34, which includes:
weedprocesses —kill -HUPis enough.expires_after_secondsvalues forjwt.signing/jwt.signing.read/jwt.filer_signing/jwt.filer_signing.read, exposed underglobal.seaweedfs.securityConfig.jwtSigning.expiresAfterSeconds. This supersedes the patch attempted in the now-closed feat(seaweedfs): expose JWTexpires_after_secondsvia values #2911.`make update` driven; patches in `patches/` (resize-api-server-annotation, disable-ca-key-rotation) reapply cleanly against 4.34.
Test plan
Summary by CodeRabbit
Release Notes – Version 4.34
New Features
Improvements
Chores