Skip to content

[Backport release-1.2] [Backport release-1.3] fix(seaweedfs): pass filer.replicas and s3.replicas to HelmRelease - #2576

Closed
github-actions[bot] wants to merge 1 commit into
release-1.2from
backport-2551-to-release-1.2
Closed

github-actions[bot] wants to merge 1 commit into
release-1.2from
backport-2551-to-release-1.2

Conversation

@github-actions

@github-actions github-actions Bot commented May 6, 2026

Copy link
Copy Markdown

Description

Backport of #2551 to release-1.2.

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]>
(cherry picked from commit 400da5e)
(cherry picked from commit d3ad21a)
@dosubot dosubot Bot added area/extra Issues or PRs related to tenant-specific modules (packages/extra/) area/storage Issues or PRs related to storage (linstor, seaweedfs, bucket, velero, harbor) kind/backport Categorizes issue or PR as requiring a backport to the current release line kind/backport-previous Categorizes issue or PR as requiring a backport to the previous release line labels May 6, 2026
@myasnikovdaniil

Copy link
Copy Markdown
Contributor

Duplicate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/extra Issues or PRs related to tenant-specific modules (packages/extra/) area/storage Issues or PRs related to storage (linstor, seaweedfs, bucket, velero, harbor) kind/backport Categorizes issue or PR as requiring a backport to the current release line kind/backport-previous Categorizes issue or PR as requiring a backport to the previous release line

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants