SeaweedFS Connect Migration Guide

Summary

Starting with Connect 1.30.0, SeaweedFS is the default object store for Utilihive. Connect Helm charts continue to support MinIO, which you can configure through Helm override values.

GridOS Foundation provides the object store. Connect services use it to store backups, flow side-channeling data, and other data. You can configure Connect to use either SeaweedFS or MinIO, and it also supports AWS S3.

SeaweedFS is not supported in Connect versions earlier than 1.30.0. If you use an earlier version of Connect, continue to use MinIO as the object store.

To continue using MinIO with Connect 1.30.0 or later, set the Helm override values described in this guide.

Enable SeaweedFS in Foundation

Before Connect can use SeaweedFS, it must be available in your Foundation environment:

Enable SeaweedFS in Foundation. Follow the Foundation installation documentation for enabling the SeaweedFS object store.
Migrate existing data from MinIO to SeaweedFS. If you have existing object data in MinIO, follow the Foundation MinIO-to-SeaweedFS migration guide to move it before switching Connect over.

S3 Buckets Used by Connect

Connect uses the following S3 buckets for object storage:

foundation-pf: default bucket created by Foundation used for backups (for example PostgreSQL and OpenBao).
connect-flowserver-side-channeling: default bucket for flow side-channeling. For large messages, Connect writes the full payload to object storage and passes only a small reference (metadata and object key) through the normal flow processing path. This keeps processing lightweight while preserving access to the full payload.
connect-flowserver-archive-verification: bucket used by deployment verification workflows.

Foundation creates these buckets when you configure either minio-tenant or seaweedfs-tenant. The following example shows the required Connect configuration, as provided in the foundation-connect-overrides release artifact.

# Chart: minio-tenant
# Ref: https://github.software.gevernova.com/grid-platform/foundation-charts/tree/release/26r04/charts/minio-tenant
minio-tenant:
  tenant:
    tenant:
      buckets:
      - name: foundation-pf
      - name: connect-flowserver-archive-verification
      - name: connect-flowserver-side-channeling

# Chart: seaweedfs-tenant
# Ref: https://github.software.gevernova.com/grid-platform/foundation-charts/tree/release/26r04/charts/seaweedfs-tenant
seaweedfs-tenant:
  seaweedfs:
    buckets:
    - name: foundation-pf
    - name: connect-flowserver-archive-verification
    - name: connect-flowserver-side-channeling

Select the Object Store in Connect

Connect selects its object store from two global Helm values:

Value Default Description

Value	Default	Description
`global.seaweedfs.enabled`	`true` (Connect >= 1.30.0)	Enables SeaweedFS as the object store. In the `connect` chart, this configures the in-cluster SeaweedFS endpoint and source secrets automatically.
`global.minio.enabled`	`true` (Connect < 1.30.0)	Enables MinIO as the object store. In the `connect` chart, this configures the in-cluster MinIO endpoint and source secrets automatically.

global.seaweedfs.enabled

true (Connect >= 1.30.0)

Enables SeaweedFS as the object store. In the connect chart, this configures the in-cluster SeaweedFS endpoint and source secrets automatically.

global.minio.enabled

true (Connect < 1.30.0)

Enables MinIO as the object store. In the connect chart, this configures the in-cluster MinIO endpoint and source secrets automatically.

Enable only one object store. If you set both global.minio.enabled and global.seaweedfs.enabled to true, the Helm chart fails with a validation error.

In connect-openbao and connect-postgresql, these values only configure the in-cluster endpoint. They do not populate the backup or restore credentials secret. To copy in the correct source secret (minio1-secret or seaweedfs1-secret), also enable secretManager.enabled and configure secretManager.secrets, or provide your own secret through s3CommonConfig.auth.secretName. This only applies if you use s3BackupConfig or s3RestoreConfig in those charts. Otherwise, the object store value has no effect.

Each of the following charts includes these values, and each chart deploys as a separate Helm release. Set the values consistently across all three charts:

connect
connect-postgresql
connect-openbao

SeaweedFS (default)

To use SeaweedFS, enable it and disable MinIO in each chart:

global:
  minio:
    enabled: false
  seaweedfs:
    enabled: true

MinIO

To continue using MinIO as the object store, enable it and disable SeaweedFS in each chart:

global:
  minio:
    enabled: true
  seaweedfs:
    enabled: false

Apply these values to the connect, connect-postgresql, and connect-openbao releases. For guidance on applying Helm value overrides, see Chart value override recommendations.

If both global.minio.enabled and global.seaweedfs.enabled are false, Connect falls back to a plain S3 configuration that uses global.s3.* (endpoint, credentials, and CA). This fallback is intended for external S3-compatible storage. Set those values explicitly.