Object Storage on Cozystack

Storage Pools

Mon, 01 Jan 0001 00:00:00 +0000

Storage pools let you partition SeaweedFS volume servers by disk type. Each pool creates a separate Volume StatefulSet tagged with a SeaweedFS diskType, and a matching set of COSI resources (BucketClasses and BucketAccessClasses) that buckets can reference.

When to Use Pools

Use storage pools when your cluster has different storage tiers and you want to control which tier a bucket uses. For example, you might have fast NVMe drives for hot data and large HDD drives for archival storage.

Buckets and Users

Mon, 01 Jan 0001 00:00:00 +0000

The Bucket application creates an S3 bucket via COSI and provisions per-user credentials as Kubernetes Secrets.

Creating a Bucket

A minimal bucket uses the default BucketClass and creates no users:

apiVersion: apps.cozystack.io/v1alpha1
kind: Bucket
metadata:
 name: my-bucket
 namespace: tenant-example
spec: {}

This provisions a BucketClaim against the default BucketClass (tenant-example). To make the bucket useful, add at least one user (see Users below).

Selecting a Storage Pool

If your SeaweedFS instance defines storage pools, use the storagePool field to target a specific pool:

SeaweedFS capacity for backups

Mon, 01 Jan 0001 00:00:00 +0000

A SeaweedFS instance starts with two volume servers of volume.size: 10Gi each and replicationFactor: 2, so every byte it stores lands on both servers and the instance holds a little under 10 GiB of objects. That is enough for occasional backups and restores. It is not enough for continuous WAL archiving from a Postgres cluster that writes steadily: WAL is archived around the clock and kept for the whole retention window, so the bucket grows until the window is full, and an instance sized by default runs out long before then.