-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
COSI v1alpha2 feature addition: 1-to-many bucketaccess:bucket relationship design #5219
base: master
Are you sure you want to change the base?
Conversation
BlaineEXE
commented
Mar 26, 2025
- One-line PR description: Follow-up from Cosi v1alpha2 changes #4599 that adds net new features to the COSI v1alpha2 spec.
- Issue link: Object Storage Support (COSI) #1979
- Other comments:
Skipping CI for Draft Pull Request. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: BlaineEXE The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
ad0836e
to
78b8792
Compare
Update the COSI KEP's base design to v1alpha2. The primary purpose of this work is to reshape the doc and spec to fix inconsistencies and vestigial items, and fix the most glaring issues in the v1alpha1 spec. COSI maintainers are planning follow-up items to add larger individual features after this. Notably, bucketInfo.json has been changed to individual secret fields with COSI_<KEY>: <VALUE> format, as the JSON blob was flagged as a problem by several v1alpha1 users. Signed-off-by: Blaine Gardner <[email protected]>
Add support to the COSI KEP for a single BucketAccess to reference multiple BucketClaims. This is a highly requested feature that allows COSI to support legacy applications that don't support buckets with independent users/accesses. Signed-off-by: Blaine Gardner <[email protected]>
78b8792
to
d333b38
Compare
|
||
These properties will be specified in the BucketRequest and follow the same pattern of events as Bucket creation. i.e. Bucket API object will be updated to reflect the properties set in BucketRequest, and then a controller will pick-up these changes and call the appropriate APIs to reflect them in the backend. | ||
The COSI Controller will update the status field of the BucketClaim object accordingly based on the status field of the Bucket object to indicate the new snapshot is ready to be used or failed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"new snapshot"? do you mean "new bucket?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please refrain from commmenting on this PR while it is still in draft state. You're commenting on changes from a different PR, and I'd prefer this discussion not get overpolluted with comments before it's ready.
If you'd like to review, please focus here: #4599