object: add bucketMaxObjects & bucketMaxSize to obc

Two new keys are added to ObjectBucketClaim.spec.additionalConfig to
support the configuration of bucket scope quota(s). This differs from
the existing maxObjects & maxSize keys, which manage a user scope
quota(s) on the automatically generated rgw user.

Signed-off-by: Joshua Hoblitt <josh@hoblitt.com>
This commit is contained in:
Joshua Hoblitt committed 2024-10-23 14:39:38 -07:00
1 parent f8a820683e
commit f51cfbdf6b
4 files changed
+360 -123

No files matched your search

@@ -32,6 +32,8 @@ spec:
additionalConfig: [6]
maxObjects: "1000"
maxSize: "2G"
bucketMaxObjects: "3000"
bucketMaxSize: "4G"
```
1. `name` of the `ObjectBucketClaim`. This name becomes the name of the Secret and ConfigMap.
@@ -45,8 +47,10 @@ If both `bucketName` and `generateBucketName` are blank or omitted then the stor
5. `storageClassName` which defines the StorageClass which contains the names of the bucket provisioner, the object-store and specifies the bucket retention policy.
6. `additionalConfig` is an optional list of key-value pairs used to define attributes specific to the bucket being provisioned by this OBC. This information is typically tuned to a particular bucket provisioner and may limit application portability. Options supported:
* `maxObjects`: The maximum number of objects in the bucket
* `maxSize`: The maximum size of the bucket, please note minimum recommended value is 4K.
* `maxObjects`: The maximum number of objects in the bucket as a quota on the user account automatically created for the bucket.
* `maxSize`: The maximum size of the bucket as a quota on the user account automatically created for the bucket. Please note minimum recommended value is 4K.
* `bucketMaxObjects`: The maximum number of objects in the bucket as an individual bucket quota. This is useful when the bucket is shared among multiple users.
* `bucketMaxSize`: The maximum size of the bucket as an individual bucket quota.
### OBC Custom Resource after Bucket Provisioning