-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Deploy COSI driver in Rook #7843
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
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions. |
Any update to this? definitely thumbs up for this feature! |
Please refer ceph/ceph-cosi#4 for details. We are waiting on the COSI team to wrap up things. Then ceph-cosi driver will updated and after that it can be consumed in Rook |
@thotz I think this has slipped from k8s 1.23. Is that your understanding as well. |
@BlaineEXE Yaa atleast atleast from KEP review thats correct, I will confirm it with next COSI call |
I think it would be good to make a CRD for deploying COSI instead of putting options on the operator. There are a lot of good tools for helping people auto-fill manifests based on CRD info, and it is a much better experience than loading a bunch more operator params. |
@thotz Is there a design doc in progress for COSI integration? This would be a good topic to discuss. My initial thought was to follow the pattern of the CSI settings since there is one driver per operator like CSI, but I can certainly see the point that a CRD is appropriate too. |
The first draft for the design doc for ceph cosi driver with Rook Resolves rook#7843 Signed-off-by: Jiffin Tony Thottan <[email protected]>
The first draft for the design doc for ceph cosi driver with Rook Resolves rook#7843 Signed-off-by: Jiffin Tony Thottan <[email protected]>
The first draft for the design doc for ceph cosi driver with Rook Resolves rook#7843 Signed-off-by: Jiffin Tony Thottan <[email protected]>
The first draft for the design doc for ceph cosi driver with Rook Resolves rook#7843 Signed-off-by: Jiffin Tony Thottan <[email protected]>
The first draft for the design doc for ceph cosi driver with Rook Resolves rook#7843 Signed-off-by: Jiffin Tony Thottan <[email protected]>
The first draft for the design doc for ceph cosi driver with Rook Resolves rook#7843 Signed-off-by: Jiffin Tony Thottan <[email protected]>
The first draft for the design doc for ceph cosi driver with Rook Resolves rook#7843 Signed-off-by: Jiffin Tony Thottan <[email protected]>
The first draft for the design doc for ceph cosi driver with Rook Resolves rook#7843 Signed-off-by: Jiffin Tony Thottan <[email protected]>
The first draft for the design doc for ceph cosi driver with Rook Resolves rook#7843 Signed-off-by: Jiffin Tony Thottan <[email protected]>
The first draft for the design doc for ceph cosi driver with Rook Resolves rook#7843 Signed-off-by: Jiffin Tony Thottan <[email protected]>
Reopening as only the design doc was merged |
The first draft for the design doc for ceph cosi driver with Rook Resolves rook#7843 Signed-off-by: Jiffin Tony Thottan <[email protected]>
The first draft for the design doc for ceph cosi driver with Rook Resolves rook#7843 Signed-off-by: Jiffin Tony Thottan <[email protected]>
@thotz can we close this? |
Yes we can there are issues to track pending work in cosi-controller |
Is this a bug report or feature request?
What should the feature do:
The Kubernetes 1.22 is planned to provide a new standard way for provisioning object store via COSI. Rook needs to deploy COSI driver to handle the incoming
BucketRequest
andBucketAccessRequest
similar to pvc requestsWhat is the use case behind this feature:
Provisioning object store via
BucketRequest
andBucketAccessRequest
The text was updated successfully, but these errors were encountered: