Going Deeper: Rook-Ceph Object StorageClass
In the previous article, we present steps for deploying rook-ceph object storageclass. This article explains what happens at each step.
The following figure summarizes the steps with operations behind the scenes.
The solid-line boxes are the operations that we perform and the dotted-line boxes are the operations that are performed by the rook-ceph operator.
When a Ceph object store is created, the cosi Ceph RGW user is created with user and bucket caps. COSI stands for Container Object Storage Interface. As of now with rook-ceph version 1.14, the Ceph COSI driver in experimental mode. The version we used was v1.13.3.
This cosi client is used later for object bucket claims. The information for the access and secret keys will be stored in the rook-ceph-object-user-object-store-cosi secret.
The object storageclass is deployed and supported by the object store.
Now, once the storageclass is created, we can create OBC (object bucket claim). When a OBC is created, a matching Ceph client will be created on a Ceph cluster. On Kubernetes side, a configmap and a secret will be created on the same namespace where the OBC is created. The names of these are the same as that of the OBC. The configmap contains bucket-related information such as bucket host…
