fix(seaweedfs): bump the COSI driver to v0.4.0 for the lost-grant fix

seaweedfs-cosi-driver v0.3.1 grants access by rewriting the legacy
/etc/iam/identity.json. Each S3 gateway migrates that file to
per-identity files and renames it away whenever it changes, so a grant
written while a gateway is migrating is lost: the BucketAccess reports
accessGranted and its Secret is written, but every gateway rejects the
key with InvalidAccessKeyId and never recovers. Users added to a Bucket
in one change lose a key regularly. v0.4.0 also writes the per-identity
file on grant.

The rest of v0.4.0 does not reach the platform. The
readwrite-governance-bypass access policy is opt-in and no
BucketAccessClass uses it. The refusal to delete a bucket that still
holds locked objects applies only to object-lock buckets, and their
classes are Retain, so the sidecar never calls DriverDeleteBucket for
them.

Assisted-by: LLM
Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
This commit is contained in:
Myasnikov Daniil committed 2026-11-12 07:53:34 +00:00
1 parent 9978771858
commit 6a93765351
3 files changed
+8 -5

No files matched your search

@@ -1 +1 @@
ghcr.io/seaweedfs/seaweedfs-cosi-driver:v0.3.1
ghcr.io/seaweedfs/seaweedfs-cosi-driver:v0.4.0
@@ -7,7 +7,7 @@ suite: seaweedfs COSI driver image pin
# BucketAccess and ignores the accessPolicy parameter. The chart ships a
# -readonly BucketAccessClass with parameters.accessPolicy: readonly, so on
# v0.1.2 a credential meant to be read-only is silently granted read-write.
# The package values.yaml overrides cosi.image to v0.3.1, which honours
# The package values.yaml overrides cosi.image to v0.4.0, which honours
# accessPolicy: readonly.
#
# This test does not set the image itself; it relies on the package values.yaml
@@ -25,7 +25,7 @@ release:
namespace: cozy-seaweedfs
tests:
- it: pins the cosi-driver container to v0.3.1 (read-only access enforcement)
- it: pins the cosi-driver container to v0.4.0 (read-only access enforcement)
template: charts/seaweedfs/templates/cosi/cosi-deployment.yaml
set:
seaweedfs.cosi.enabled: true
@@ -35,4 +35,4 @@ tests:
value: seaweedfs-cosi-driver
- equal:
path: spec.template.spec.containers[0].image
value: ghcr.io/seaweedfs/seaweedfs-cosi-driver:v0.3.1
value: ghcr.io/seaweedfs/seaweedfs-cosi-driver:v0.4.0
+4 -1
View File
@@ -303,7 +303,10 @@ seaweedfs:
# S3 actions for every BucketAccess and ignores the accessPolicy parameter.
# v0.3.x honours accessPolicy: readonly, so a -readonly BucketAccessClass
# actually issues read-only (Read,List) credentials instead of read-write.
image: "ghcr.io/seaweedfs/seaweedfs-cosi-driver:v0.3.1"
# v0.4.0 also writes each grant to the per-identity IAM file: v0.3.1
# rewrites only the legacy identity.json, which the S3 gateways migrate
# concurrently, so a grant could be lost for good.
image: "ghcr.io/seaweedfs/seaweedfs-cosi-driver:v0.4.0"
podLabels:
policy.cozystack.io/allow-to-apiserver: "true"
driverName: "seaweedfs.objectstorage.k8s.io"