You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8348f96
Browse filesBrowse the repository at this point in the historyBrowse files
## What this PR does
Re-vendors the SeaweedFS Helm chart from 4.05 (chart 4.0.405) to 4.31
(chart 4.31.0) via `make update`, and adapts the package layer to the
breaking changes that accumulated across the gap.
What lands with the bump: the PostgreSQL filer store (the backend used
here) moves to pgx v5 with PgBouncer support and an `ON CONFLICT` upsert
default; HTTPS certificates hot-reload without a pod restart on
cert-manager rotation; more S3 and volume Prometheus metrics are
exported, and the S3 Service now exposes a metrics port by default.
Package-layer adaptations:
- **Dropped `s3-traffic-distribution.patch`.** Native
`s3.trafficDistribution` support landed upstream in chart 4.12. The
native field is gated to Kubernetes >= 1.31 and auto-converts
`PreferClose` to `PreferSameZone` on >= 1.35, which the hardcoded patch
did not do. The patch is replaced with `s3.trafficDistribution:
PreferClose` in the package values, plus helm-unittest coverage pinning
all three version cases.
- **Migrated `global.*` to `global.seaweedfs.*`.** Chart 4.18 namespaced
the app-specific globals to avoid polluting the shared global namespace
when the chart is used as a subchart. The package values move
`enableSecurity`, `serviceAccountName`, `extraEnvironmentVars` and
`monitoring` to the new path instead of relying on the chart's
backward-compat shim.
Verified with `helm template` and `helm unittest`: the cluster env vars
reach the pods, the gRPC mTLS `security.toml` renders intact (including
the new admin/worker sections from the 4.24/4.26 security tightening),
and both retained patches still apply.
### Screenshots
N/A — no UI changes.
### Release note
```release-note
chore(seaweedfs): bump SeaweedFS to 4.31
```
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
* **New Features**
* OpenShift support and dedicated values for secure deployments
* S3 Iceberg gateway with optional ingress and service settings
* Volume UI ingress support and RocksDB variant guidance
* Grafana: new “Upload Errors” panel
* **Bug Fixes**
* Improved S3 traffic distribution handling across Kubernetes versions
* **Documentation**
* Expanded README: DB init, admin secret options, worker job types,
OpenShift notes
* **Chores**
* Helm chart bumped to 4.31.0; values restructured for SeaweedFS and
COSI bucket class simplified
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
* master/filer/volume are stateful sets with anti-affinity on the hostname,
25
24
so your deployment will be spread/HA.
26
25
* chart is using memsql(mysql) as the filer backend to enable HA (multiple filer instances) and backup/HA memsql can provide.
27
-
* mysql user/password are created in a k8s secret (secret-seaweedfs-db.yaml) and injected to the filer with ENV.
26
+
* mysql user/password are created in a k8s secret (default: `<release>-seaweedfs-db-secret`) and injected to the filer with ENV.
28
27
* cert config exists and can be enabled, but not been tested, requires cert-manager to be installed.
29
28
30
29
## Prerequisites
@@ -35,7 +34,9 @@ leveldb is the default database, this supports multiple filer replicas that will
35
34
When the [limitations](https://github.com/seaweedfs/seaweedfs/wiki/Filer-Store-Replication#limitation) apply, or for a large number of filer replicas, an external datastore is recommended.
36
35
37
36
Such as MySQL-compatible database, as specified in the `values.yaml` at `filer.extraEnvironmentVars`.
38
-
This database should be pre-configured and initialized by running:
37
+
This database should be pre-configured and initialized. If using the default `db-init-config`, the configmap name is now dynamic (e.g., `<release>-seaweedfs-db-init-config`). You can override this name via `filer.dbInitConfigName`.
38
+
39
+
To initialize manually:
39
40
```sql
40
41
CREATETABLEIF NOT EXISTS `filemeta` (
41
42
`dirhash`BIGINTNOT NULL COMMENT 'first 64 bits of MD5 hash value of directory field',
@@ -48,6 +49,35 @@ CREATE TABLE IF NOT EXISTS `filemeta` (
48
49
49
50
Alternative database can also be configured (e.g. leveldb, postgres) following the instructions at `filer.extraEnvironmentVars`.
50
51
52
+
#### RocksDB variant
53
+
54
+
The `_large_disk_rocksdb` image tag ships with RocksDB pre-configured as the filer backend.
55
+
To use this image with the Helm chart, override the image on all three components and disable
56
+
the chart's default `WEED_LEVELDB2_ENABLED`, which would otherwise re-enable LevelDB2 and
57
+
override the image's built-in RocksDB configuration:
58
+
59
+
```yaml
60
+
# Replace <VERSION> with the desired seaweedfs version, e.g. 3.80_large_disk_rocksdb.
SeaweedFS can be deployed on OpenShift or any cluster enforcing the Kubernetes "restricted" Pod Security Standard. By default, OpenShift blocks containers that run as root or use `hostPath` volumes.
371
+
372
+
To deploy on OpenShift, use the provided `openshift-values.yaml` which overrides the default configuration to:
373
+
1. Use `PersistentVolumeClaims` instead of `hostPath`.
374
+
2. Enable `runAsNonRoot` and omit hardcoded UIDs to allow OpenShift to assign valid UIDs automatically.
375
+
3. Apply appropriate `seccompProfile` and drop capabilities.
376
+
377
+
Usage:
378
+
```bash
379
+
helm install seaweedfs seaweedfs/seaweedfs \
380
+
-n seaweedfs --create-namespace \
381
+
-f openshift-values.yaml
382
+
```
383
+
333
384
## Enterprise
334
385
335
386
For enterprise users, please visit [seaweedfs.com](https://seaweedfs.com) for the SeaweedFS Enterprise Edition,
336
-
which has a self-healing storage format with better data protection.
387
+
which has advanced features, including data recovery, self-healing storage, customizable erasure coding, EC vacuum and repair, etc.
0 commit comments