Skip to content

[SeaweedFS] Disable ClusterRole for SeaweedFS installation #280

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.

Sign up for GitHub

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

Merged
shay79il merged 1 commit into from
Mar 19, 2026
+9 −1
Merged

[SeaweedFS] Disable ClusterRole for SeaweedFS installation #280

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion charts/mlrun-ce/Chart.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
apiVersion: v1
name: mlrun-ce
version: 0.11.0-rc.26
version: 0.11.0-rc.27
description: MLRun Open Source Stack
home: https://iguazio.com
icon: https://www.iguazio.com/wp-content/uploads/2019/10/Iguazio-Logo.png
Expand Down
4 changes: 4 additions & 0 deletions charts/mlrun-ce/non_admin_cluster_ip_installation_values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,10 @@ mpi-operator:

seaweedfs:
enabled: true
adminService:
type: ClusterIP
port: 23646
nodePort: ""
s3Service:
type: ClusterIP
port: 8333
Expand Down
4 changes: 4 additions & 0 deletions charts/mlrun-ce/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -301,6 +301,10 @@ seaweedfs:
registry: ""
# Override default "001" to "000" for single-node setup (no replication)
replicationPlacement: "000"
# Disabled by default. Only needed if SeaweedFS master/volume pods need to
# delete other pods during data migration (e.g., multi-node rebalancing).
# Enabling this creates a ClusterRole, which conflicts in multi-NS deployments.
createClusterRole: false

# Master server - metadata management
master:
Expand Down
Loading