Hi Rajesh,
> How are applications supposed to use the bucket credentials from the BucketAcceesResponse?
Those credentials returned by the driver are put into the secret, which is created by
COSI Sidecar. You can refer to
Ceph COSI deployment manifests to see how the COSI Sidecar is deployed. Right now, the users are expected to either:
a) Modify application code to parse the COSI secret;
b) Use
init container with custom logic to parse the COSI secret and create a configuration that can be read by the application;
> How do they create/delete objects in those buckets?
> Are applications supposed to use S3 clients (or equivalent) for object management?
Yes, exactly. Your application needs to be able to access object storage by internal logic. COSI provides only the Kubernetes-native object storage management.
> If applications are supposed to manage objects themselves then what's the value of COSI, only bucket management?
Buckets are a storage solution logically equivalent to Volumes. Most applications are not delegating writing data to disk to external programs, and this is also expected from applications making use of Buckets provisioned by COSI.
COSI provides a simplified solution to the management of object storage platforms, while providing standardised API for all vendors willing to integrate with it.
I hope my answers clarified your doubts a little bit. If you still have some more questions, don't be afraid to ask, I am more than happy to provide any additional information.