Docs | Bucket Types #1448
Draft
Docs | Bucket Types #1448
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Ben <[email protected]>
| Namespace buckets work differently than data buckets, since they try¹ to not apply any processing on the objects that are uploaded to them, and act as more of a 'passthrough'. | ||
| The objects can be accessed both from within NooBaa, as well as from whatever storage providers hosts them. | ||
|
|
||
| <sup><sub>1. In some cases, object metadata (such as tags) might have to be modified in order to comply with a cloud provider's limits</sub></sup> |
There was a problem hiding this comment.
- would mention the types of NS we supports.
- Add that when the underlying storage does not support S3 , NooBaa performs the logic and semantics on top what is supported by the underlying storage
doc/bucket-types.md
Outdated
|
|
||
| Once a store is created, it's necessary to create a [bucketclass](bucket-class-crd.md) resource. Bucketclasses allow users to define bucket policies relating to data placement and replication, and are used as a middle layer between buckets and stores. | ||
|
|
||
| After the bucketclass has been created, it's now finally possible to create an [object bucket claim](obc-provisioner.md), which is then reconciled by NooBaa and creates a bucket in the system. |
There was a problem hiding this comment.
Add a section of what is supported which each bucket which will point to the S3 compatibility doc (see my other comment there)
Signed-off-by: Ben <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Explain the changes