-
Notifications
You must be signed in to change notification settings - Fork 693
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
New Repository for Container Object Storage Interface implementation #1942
Comments
/assign @saad-ali |
/sig storage |
WRT to
See too #1904 |
Can you send an email to sig-storage mailing list about this request? |
thanks. I just sent out email about the request. |
Suggestions:
|
@saad-ali While we haven't hammered out a complete design for automation, it would still be beneficial to have a common space for prototyping. Is this work something we should handle out of band? |
I guess my concern is are you boxing yourself in by having a single repo called |
Fair point, I think we'd be fine then with your suggested repos, with the architecture to follow once the design is settled on:
|
I have updated the issue and I believe this will give us the start we need right now. |
/lgtm |
/assign |
The repos have been created:
Also created:
Once both PRs merge, we can close this issue. |
All PRs have merged :) /close |
@nikhita: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
New Repo, Staging Repo, or migrate existing
new repository
Requested name for new repository
container-object-storage-interface-spec (Container Object Storage Specification)
container-object-storage-interface-csi-adapter (CSI driver to bootstrap COSI workloads)
Which Organization should it reside
kubernetes-sigs
If not a staging repo, who should have admin access
@jsafrane
@msau42
@saad-ali
@xing-yang
If not a staging repo, who should have write access
@saad-ali
@jsafrane
@msau42
@xing-yang
@copejon
@wlan0
@brahmaroutu
If not a staging repo, who should be listed as approvers in OWNERS
@jsafrane
@msau42
@saad-ali
@xing-yang
If not a staging repo, who should be listed in SECURITY_CONTACTS
@jsafrane
@msau42
@saad-ali
@xing-yang
What should the repo description be
Kubernetes specific Container Object Storage Interface (COSI) components
What SIG and subproject does this fall under in sigs.yaml
this is a new subproject for sig-storage called kubernetes-cosi
Approvals
Please prove you have followed the appropriate approval process for this new
repo by including links to the relevant approvals (meeting minutes, e-mail
thread, etc.)
Need sig-storage approval from: @saad-ali and @xing-yang
Please refer to KEP: kubernetes/enhancements#1383
Authoritative requirements are here: https://git.k8s.io/community/github-management/kubernetes-repositories.md
tl;dr (but really you should read the linked doc, this may be stale)
in that SIG's charter
Additional context for request
Since the design mentioned in the KEP constitute multiple components, this issue is requesting for multiple repos under new subproject(Kubernetes-cosi) that belongs to sig-storage.
The text was updated successfully, but these errors were encountered: