Repository navigation
fix(seaweedfs): pass filer.replicas and s3.replicas to HelmRelease - #2533
Conversation
The filer and s3 blocks in the seaweedfs HelmRelease values omitted the replicas: field, so user-supplied .Values.filer.replicas and .Values.s3.replicas were silently ignored and the upstream chart defaults took over. This also caused the WorkloadMonitor resources for filer and s3 (which read the same values) to diverge from the actual replica count and trigger spurious alerts when users set non-default values. Mirror the master/volume/db pattern and interpolate replicas: into both blocks. Assisted-By: Claude <[email protected]> Signed-off-by: Aleksei Sviridkin <[email protected]>
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request addresses an issue where custom replica counts for the filer and s3 components were being ignored in the SeaweedFS Helm deployment. By correctly passing these values through the template, the configuration now respects user overrides and ensures that monitoring resources remain synchronized with the actual deployment state. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on Gemini (@gemini-code-assist) comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe SeaweedFS Helm template is updated to support configurable replica counts for the filer and s3 components via Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 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)
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. Review rate limit: 7/8 reviews remaining, refill in 7 minutes and 30 seconds.Comment |
IvanHunters
left a comment
There was a problem hiding this comment.
filer.replicas and s3.replicas both have defaults in values.yaml, and the WorkloadMonitor for filer was already reading .Values.filer.replicas for alerting — so the monitor was counting against a different value than what the chart actually deployed. The fix is consistent with the db / master / volume pattern.
LGTM
|
Successfully created backport PR for |
What this PR does
The
filerands3blocks in the seaweedfs HelmRelease values omitted thereplicas:field, so user-supplied.Values.filer.replicasand.Values.s3.replicaswere silently ignored and the upstream chart defaults took over. As a second-order effect, theWorkloadMonitorresources forfilerands3(which read the same values) diverged from the actual replica count and could trigger spurious alerts when users set non-default values.This PR mirrors the existing
master/volume/dbpattern and interpolatesreplicas:into both blocks.Fixes #2531
Release note
Summary by CodeRabbit
Release Notes