Skip to content

chore: keep master statefulSet chart up-to-date #6903

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

YixingCheng
Copy link
Contributor

What problem are we solving?

This patch adds some missing master options to the helm chart of master statefulSet.

How are we solving the problem?

Lifting the master options from master.go to the chart

How is the PR tested?

Tested by editing the master statefulSet in an existing k8s cluster

kg sts seaweedfs-master -oyaml
...
      - command:
        - /bin/sh
        - -ec
        - |
          exec /usr/bin/weed \
          -logtostderr=true \
          -v=1 \
          master \
          -port=9333 \
          -mdir=/data \
          -ip.bind=0.0.0.0 \
          -defaultReplication=000 \
          -metricsPort=9324 \
          -volumeSizeLimitMB=1000 \
          -raftHashicorp \
          -raftBootstrap \
          -electionTimeout="5s" \
          -heartbeatInterval="500ms" \
          -ip=${POD_NAME}.${SEAWEEDFS_FULLNAME}-master.vmsp-platform \
          -peers=${SEAWEEDFS_FULLNAME}-master-0.${SEAWEEDFS_FULLNAME}-master.vmsp-platform:9333,${SEAWEEDFS_FULLNAME}-master-1.${SEAWEEDFS_FULLNAME}-master.vmsp-platform:9333,${SEAWEEDFS_FULLNAME}-master-2.${SEAWEEDFS_FULLNAME}-master.vmsp-platform:9333
...

Checks

  • I have added unit tests if possible.
  • I will add related wiki document changes and link to this PR after merging.

This patch adds some missing master options to the helm chart of master statefulSet.
@chrislusf chrislusf merged commit 5a7d226 into seaweedfs:master Jun 21, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants