Skip to content

feat(seaweedfs-cosi-driver): support Object Lock and read-only bucket access #1921

Closed

Description

@kvaps

Overview

Add support for creating buckets with Object Lock (WORM) and granting read-only access through COSI driver.

Use cases

  1. Object Lock (WORM) — automatically create buckets with immutable storage protection via BucketClass parameters
  2. Read-only access — grant read-only credentials to buckets via BucketAccessClass parameters

Desired behavior

apiVersion: objectstorage.k8s.io/v1alpha1
kind: BucketClass
metadata:
  name: immutable-storage
driverName: seaweedfs.objectstorage.k8s.io
parameters:
  objectLockEnabled: "true"
---
apiVersion: objectstorage.k8s.io/v1alpha1
kind: BucketAccessClass
metadata:
  name: readonly
driverName: seaweedfs.objectstorage.k8s.io
authenticationType: Key
parameters:
  accessPolicy: "readonly"

Blocked by

Related

Activity

  1. added
    kind/featureCategorizes issue or PR as related to a new feature
    on Jan 27, 2026
  2. dosubot commented on Apr 28, 2026

    @dosubot

    Hi, Andrei Kvapil (@kvaps). I'm Dosu, and I'm helping the cozystack team manage their backlog and am marking this issue as stale.

    Issue Summary:

    • You proposed enhancing the seaweedfs COSI driver to support bucket creation with Object Lock (WORM) and enable read-only access via BucketClass and BucketAccessClass parameters.
    • This enhancement aims to provide automatic immutable storage protection and manage read-only credentials.
    • The implementation is currently on hold pending clarification on parameter usage in the upstream COSI specification.
    • There has been no further activity or comments on this issue since the initial proposal.

    Next Steps:

    • Please let us know if this issue is still relevant to the latest version of the cozystack repository by commenting here.
    • If we do not hear back within 7 days, this issue will be automatically closed.

    Thank you for your understanding and contribution!

  3. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale
    and removed on May 1, 2026
  4. added a commit that references this issue on Jun 30, 2026
    eab9b03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

kind/featureCategorizes issue or PR as related to a new featurelifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions