-
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 - controller and provisioner #2039
Labels
area/github-repo
Creating, migrating or deleting a Kubernetes GitHub Repository
sig/storage
Categorizes an issue or PR as relevant to SIG Storage.
Comments
brahmaroutu
added
the
area/github-repo
Creating, migrating or deleting a Kubernetes GitHub Repository
label
Jul 16, 2020
/sig storage |
k8s-ci-robot
added
the
sig/storage
Categorizes an issue or PR as relevant to SIG Storage.
label
Jul 16, 2020
+1 |
@nikhita Please help us get these two repos created. |
/assign will do in a bit |
This was referenced Jul 22, 2020
Repos have been created:
Also created:
Once both PRs get merged, we can close this issue. |
Teams have been granted access and repo has been added to sigs.yaml. Closing. |
Awesome, thanks for quick turnaround. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/github-repo
Creating, migrating or deleting a Kubernetes GitHub Repository
sig/storage
Categorizes an issue or PR as relevant to SIG Storage.
New Repo, Staging Repo, or migrate existing
New Repo
Requested name for new repository
container-object-storage-interface-controller (Container Object Storage Controller)
container-object-storage-interface-provisioner-sidecar (Provisioner logic to interface with COSI driver)
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
@rrati
@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
Container Object Storage Interface (COSI) controller responsible to manage lifecycle of COSI objects
Container Object Storage Interface (COSI) provisioner responsible to interface with COSI drivers
What SIG and subproject does this fall under in sigs.yaml
SIG: sig-storage, subproject: 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
To run proof of concept of the design outlined in the above mentioned KEP, we need these two repos to continue works and eventually build an alpha version of the controller and provisioner into these repos.
The text was updated successfully, but these errors were encountered: