object: intial cosi driver controller design
Adding CephCOSIDriver CRD and controller. The controller will bring up the ceph cosi driver when first object store is created in the rook operator namespace. Then admin can defined COSI CRDs like BucketClass and BucketAccessClass for different object stores deployed via Rook. Using the BucketClass and BucketAccessClass, user can define BucketAccess for backend bucket in the RGW. The CephCOSIDriver CRD defines configuration options for ceph cosi driver. In the first version its usability is minimal. Even if it is not defined Rook will bring up the ceph cosi driver with default values. Signed-off-by: Jiffin Tony Thottan <thottanjiffin@gmail.com>
This commit is contained in:
1 parent
86630709b7
commit
b48dc8a335
46 files changed
+3466
-8
No files matched your search
@@ -208,6 +208,10 @@ function validate_yaml() {
|
||||
keda_url="https://github.com/kedacore/keda/releases/download/v${keda_version}/keda-${keda_version}.yaml"
|
||||
kubectl apply -f "${keda_url}"
|
||||
|
||||
#create the COSI CRDS
|
||||
cosi_crd_url="github.com/kubernetes-sigs/container-object-storage-interface-api"
|
||||
kubectl create -k "${cosi_crd_url}"
|
||||
|
||||
# skipping folders and some yamls that are only for openshift.
|
||||
manifests="$(find . -maxdepth 1 -type f -name '*.yaml' -and -not -name '*openshift*' -and -not -name 'scc*' -and -not -name 'psp*' -and -not -name 'kustomization*')"
|
||||
with_f_arg="$(echo "$manifests" | awk '{printf " -f %s",$1}')" # don't add newline
|
||||
|
||||
Reference in new issue
Block a user