Aleksei Sviridkin ed20a4322a fix(objectstorage-controller): propagate Bucket readiness to BucketClaim ...

The vendored COSI controller (v0.2.2) sets only BucketClaim.status.bucketName
in the dynamic-provisioning path and hardcodes bucketReady=false, never
re-reading the Bucket afterwards. The controller does not watch Buckets, so the
readiness transition the sidecar performs (false->true) is never reflected on
the BucketClaim: bucketReady stays false forever and BucketAccess is never
granted, leaving provisioned buckets without credentials.

Re-read the live Bucket after create and propagate its readiness, so the
periodic resync converges the BucketClaim to ready. This matches the behavior
the rewritten upstream controller already has on its main branch.

Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Aleksei Sviridkin <f@lex.la>

2026-06-03 01:48:30 +03:00

..

patches

fix(objectstorage-controller): propagate Bucket readiness to BucketClaim

2026-06-03 01:48:30 +03:00

Dockerfile

fix(objectstorage-controller): retry on Bucket update conflict during BucketAccess reconcile

2026-04-29 10:50:16 +05:00