Zenko CloudServer

What it is#

CloudServer is a mature implementation with the widest S3 surface of the six, and the one whose behaviour is closest to AWS on the features this driver uses. The in-memory backend below is for trying it out; use the file backend or a real Scality RING for anything you intend to keep.

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.

services:
  cloudserver:
    image: zenko/cloudserver:latest-7.70.10
    environment:
      # "mem" keeps nothing across a restart. Use S3BACKEND=file with a volume to persist.
      S3BACKEND: mem
      SCALITY_ACCESS_KEY_ID: archiver-key
      SCALITY_SECRET_ACCESS_KEY: archiver-secret
      REMOTE_MANAGEMENT_DISABLE: "1"
    ports:
      - "8000:8000"

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.

apiVersion: v1
kind: Secret
metadata:
  name: cloudserver-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: cloudserver-credentials
        volumeAttributes:
          bucket: archives
          prefix: "{namespace}/{podName}/"
          endpoint: http://cloudserver.storage.svc.cluster.local:8000
          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 Zenko CloudServer through the driver's own code paths.

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#