csi-s3-archiver
Install

S3 endpoints

Versity S3 Gateway

An S3 protocol translator over POSIX filesystems, aimed at existing HPC storage.

What it is#

VersityGW puts an S3 API over a POSIX filesystem while keeping the objects as ordinary files, so what the driver archives stays readable with ls and cat. That suits sites with existing parallel filesystems.

Projecthttps://github.com/versity/versitygw
LicenceApache-2.0
Image testedversity/versitygw:v1.0.9
S3 port7070

Run it#

A single-node setup, enough to archive into and to try the driver against. It is not a production topology for any of these products; each project's own documentation covers that.

docker-compose.yml
services:
  versitygw:
    image: versity/versitygw:v1.0.9
    command: ["--port", "0.0.0.0:7070", "posix", "/data"]
    environment:
      ROOT_ACCESS_KEY_ID: archiver-key
      ROOT_SECRET_ACCESS_KEY: archiver-secret
    ports:
      - "7070:7070"
    volumes:
      # Must exist: the posix backend chdirs into it and refuses to start otherwise.
      - versity-data:/data

volumes:
  versity-data:

Point the driver at it#

Endpoint and credentials go on the volume; nothing about the driver's installation changes. pathStyle is on because a container reached by address has no per-bucket DNS, which is the usual shape outside AWS.

a volume archiving into Versity S3 Gateway
apiVersion: v1
kind: Secret
metadata:
  name: versitygw-credentials
  namespace: default
stringData:
  accessKeyId: archiver-key
  secretAccessKey: archiver-secret
---
apiVersion: v1
kind: Pod
metadata:
  name: writer
spec:
  containers:
    - name: app
      image: busybox:1.36
      command: ["sh", "-c", "echo hello > /dumps/first.txt; sleep 3600"]
      volumeMounts:
        - { name: dumps, mountPath: /dumps }
  volumes:
    - name: dumps
      csi:
        driver: s3archiver.csi.trion.de
        nodePublishSecretRef:
          name: versitygw-credentials
        volumeAttributes:
          bucket: archives
          prefix: "{namespace}/{podName}/"
          endpoint: http://versitygw.storage.svc.cluster.local:7070
          pathStyle: "true"
          region: us-east-1

To make it the default for every volume instead, set S3A_ENDPOINT, S3A_PATH_STYLE and S3A_REGION on the DaemonSet and leave them off the volumes. The configuration reference lists both halves.

What works#

Measured, not claimed. An opt-in test suite runs every one of these against Versity S3 Gateway through the driver's own code paths.

CapabilityWhat it gives you
Single PutObjectyesArchiving anything at all.
Multipart uploadyesFiles over the 64 MiB threshold. A heapdump is almost always over it.
ListObjectsV2yesSegment compaction and durable volumes. Ephemeral archiving never lists.
DeleteObjectyesCompaction removes fragments it has assembled; durable volumes mirror deletions.
GetObjectyesRestoring a durable volume at pod start. Ephemeral volumes never read back.
UploadPartCopyyesServer-side append and segment assembly. Without it a growing file is re-uploaded whole.
Offset append 1noThe cheapest append, one request carrying only the new bytes. An S3 Express feature.
SSE-S3yesRequesting AES256 encryption per volume. A bucket default covers you regardless.
SSE-KMSyesPer-volume encryption with a customer-managed key.
Presigned PUTyesPresigned credential mode, where the node holds no S3 keys.
Presigned POST policynoSigner-less mode, with one prefix-scoped policy in the volume Secret.

9 of 11 supported. Missing: Offset append, Presigned POST policy. The driver degrades rather than failing for all of these except where noted below.

Worth knowing#