Skip to content

Commit e600529

Browse files
authored
Merge pull request #2461 from saad-ali/sig-storage-charter
SIG-storage charter
2 parents e2d5c8a + 33058d1 commit e600529

File tree

3 files changed

+72
-3
lines changed

3 files changed

+72
-3
lines changed

sig-storage/README.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,9 @@ To understand how this file is generated, see https://git.k8s.io/community/gener
88
--->
99
# Storage Special Interest Group
1010

11-
Covers storage and volume plugins.
11+
SIG Storage is responsible for ensuring that different types of file and block storage (whether ephemeral or persistent, local or remote) are available wherever a container is scheduled (including provisioning/creating, attaching, mounting, unmounting, detaching, and deleting of volumes), storage capacity management (container ephemeral storage usage, volume resizing, etc.), influencing scheduling of containers based on storage (data gravity, availability, etc.), and generic operations on storage (snapshoting, etc.).
12+
13+
The [charter](charter.md) defines the scope and governance of the Storage Special Interest Group.
1214

1315
## Meetings
1416
* Regular SIG Meeting: [Thursdays at 9:00 PT (Pacific Time)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=9:00&tz=PT%20%28Pacific%20Time%29).

sig-storage/charter.md

+61
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
# SIG Storage Charter
2+
3+
This charter adheres to the conventions described in the [Kubernetes Charter README] and uses
4+
the Roles and Organization Management outlined in [sig-governance].
5+
6+
## Scope
7+
8+
SIG Storage is responsible for ensuring that different types of file and block storage
9+
(whether ephemeral or persistent, local or remote) are available wherever a container is
10+
scheduled (including provisioning/creating, attaching, mounting, unmounting, detaching,
11+
and deleting of volumes), storage capacity management (container ephemeral storage
12+
usage, volume resizing, etc.), influencing scheduling of containers based on storage
13+
(data gravity, availability, etc.), and generic operations on storage (snapshoting, etc.).
14+
15+
### In scope
16+
17+
Some notable examples of features owned by SIG Storage:
18+
19+
* Persistent Volume Claims and Persistent Volumes
20+
* Storage Classes and Dynamic Provisioning
21+
* Kubernetes volume plugins
22+
* Container Storage Interface (CSI)
23+
* Secret Volumes, ConfigMap Volumes, DownwardAPI Volumes, EmptyDir Volumes (co-owned with SIG-Node)
24+
25+
#### Code, Binaries and Services
26+
27+
* Kubernetes internal controllers and APIs responsible for exposing file and block storage to Kubernetes workloads.
28+
* Kubernetes external sidecar containers and binaries required for exposing file and block storage to Kubernetes workloads.
29+
* Interfaces required for exposing file and block storage to Kubernetes workloads.
30+
* Unit, Integration, and End-to-End (E2E) Tests validating and preventing regressions in the above.
31+
32+
#### Cross-cutting and Externally Facing Processes
33+
34+
* Defining interface and requirements for connecting third party storage systems to Kubernetes.
35+
36+
### Out of scope
37+
38+
SIG Storage is not responsible for
39+
40+
* Data path of remote storage (GCE PD, AWS EBS, NFS, etc.)
41+
* How bits are transferred.
42+
* Where bits are stored.
43+
* Container writable layer (SIG Node handles that).
44+
* The majority of storage plugins/drivers (generally owned by storage vendors).
45+
46+
## Roles and Organization Management
47+
48+
SIG Storage adheres to the Roles and Organization Management outlined in [sig-governance]
49+
and opts-in to updates and modifications to [sig-governance].
50+
51+
### Deviations from [sig-governance]
52+
53+
SIG Storage does not have separate tech leads: SIG Storage chairs serve as tech leads.
54+
55+
### Subproject Creation
56+
57+
SIG Storage delegates subproject approval to Technical Leads. See [Subproject creation - Option 1].
58+
59+
[sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md
60+
[Kubernetes Charter README]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md
61+
[Subproject creation - Option 1]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md#subproject-creation

sigs.yaml

+8-2
Original file line numberDiff line numberDiff line change
@@ -1567,8 +1567,14 @@ sigs:
15671567
- name: Storage
15681568
dir: sig-storage
15691569
mission_statement: >
1570-
Covers storage and volume plugins.
1571-
charter_link:
1570+
SIG Storage is responsible for ensuring that different types of file and
1571+
block storage (whether ephemeral or persistent, local or remote) are
1572+
available wherever a container is scheduled (including provisioning/creating,
1573+
attaching, mounting, unmounting, detaching, and deleting of volumes), storage
1574+
capacity management (container ephemeral storage usage, volume resizing,
1575+
etc.), influencing scheduling of containers based on storage (data gravity,
1576+
availability, etc.), and generic operations on storage (snapshoting, etc.).
1577+
charter_link: charter.md
15721578
label: storage
15731579
leadership:
15741580
chairs:

0 commit comments

Comments
 (0)