-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
SIG-storage charter #2461
SIG-storage charter #2461
Conversation
/approve |
sig-storage/charter.md
Outdated
* Storage Classes and Dynamic Provisioning | ||
* Kubernetes volume plugins | ||
* Container Storage Interface (CSI) | ||
* Secret, ConfigMap, DownwardAPI Volumes |
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.
Don't know if this should be more explicit that its Secrets, ConfigMap etc related to Volumes? I know that's pretty implicit due to the doc and such but just a nit.
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.
Do we want to mention enptydir volumes too?
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.
Done!
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.
Minor nit but overall looks like a solid charter to me.
b9ae477
to
eb6db48
Compare
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.
LGTM
sig-storage/charter.md
Outdated
* Storage Classes and Dynamic Provisioning | ||
* Kubernetes volume plugins | ||
* Container Storage Interface (CSI) | ||
* Secret Volumes, ConfigMap Volumes, DownwardAPI Volumes, EmptyDirVolumes (co-owned with SIG-Node) |
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.
nit: space between EmptyDir and Volumes
/committee steering |
8480db7
to
95118a3
Compare
Can you split the sigs.yaml change out of this? @brendandburns is listed as the primary reviewer for this and is out next week. I'd like to get the sigs.yaml piece merged sooner. |
95118a3
to
30a3935
Compare
/uncc |
/lgtm cc @quinton-hoole can you take a look since @brendanburns is OOO |
/cc @michelleN |
sig-storage/charter.md
Outdated
SIG Storage delegates subproject approval to Technical Leads. See [Subproject creation - Option 1]. | ||
|
||
[sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md | ||
[sigs.yaml]: https://github.com/kubernetes/community/blob/master/sigs.yaml#L1454 |
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.
sigs.yaml seems not used and not needed here. (Also per the changes in charter template use of sigs.yaml is discouraged and recommended to be replaced with SIG's README.)
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.
This is copy paste from https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md#project-management as recommended by SIG Charter template.
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.
@saad-ali thanks, not sure if I am missing something here and if so please ignore my comment but what I noticed is,
- The charter.md seems not using sigs.yaml anywhere, so I don't think related link is needed
- Even if we are using it, then referencing it by line number is not good as numbers will change, the charter template is already modified, e0d60fd
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.
Whoops I misread this comment. I thought it was about Subproject creation
for some reason. Removed the stray sigs.yaml
link
30a3935
to
33058d1
Compare
@saad-ali :-) np, looks good to me now! |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: childsb, quinton-hoole The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Charter for @kubernetes/sig-storage-misc
/assign @childsb for initial pass. Will assign to TOC for approval once we have internal SIG storage consensus.
Also closes #2467