Skip to content
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

Merged
merged 2 commits into from
Aug 23, 2018
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion sig-storage/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,9 @@ To understand how this file is generated, see https://git.k8s.io/community/gener
--->
# Storage Special Interest Group

Covers storage and volume plugins.
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.).

The [charter](charter.md) defines the scope and governance of the Storage Special Interest Group.

## Meetings
* 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).
Expand Down
61 changes: 61 additions & 0 deletions sig-storage/charter.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,61 @@
# SIG Storage Charter

This charter adheres to the conventions described in the [Kubernetes Charter README] and uses
the Roles and Organization Management outlined in [sig-governance].

## Scope

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.).

### In scope

Some notable examples of features owned by SIG Storage:

* Persistent Volume Claims and Persistent Volumes
* Storage Classes and Dynamic Provisioning
* Kubernetes volume plugins
* Container Storage Interface (CSI)
* Secret Volumes, ConfigMap Volumes, DownwardAPI Volumes, EmptyDir Volumes (co-owned with SIG-Node)

#### Code, Binaries and Services

* Kubernetes internal controllers and APIs responsible for exposing file and block storage to Kubernetes workloads.
* Kubernetes external sidecar containers and binaries required for exposing file and block storage to Kubernetes workloads.
* Interfaces required for exposing file and block storage to Kubernetes workloads.
* Unit, Integration, and End-to-End (E2E) Tests validating and preventing regressions in the above.

#### Cross-cutting and Externally Facing Processes

* Defining interface and requirements for connecting third party storage systems to Kubernetes.

### Out of scope

SIG Storage is not responsible for

* Data path of remote storage (GCE PD, AWS EBS, NFS, etc.)
* How bits are transferred.
* Where bits are stored.
* Container writable layer (SIG Node handles that).
* The majority of storage plugins/drivers (generally owned by storage vendors).

## Roles and Organization Management

SIG Storage adheres to the Roles and Organization Management outlined in [sig-governance]
and opts-in to updates and modifications to [sig-governance].

### Deviations from [sig-governance]

SIG Storage does not have separate tech leads: SIG Storage chairs serve as tech leads.

### Subproject Creation

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
[Kubernetes Charter README]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md
[Subproject creation - Option 1]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md#subproject-creation
10 changes: 8 additions & 2 deletions sigs.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -1550,8 +1550,14 @@ sigs:
- name: Storage
dir: sig-storage
mission_statement: >
Covers storage and volume plugins.
charter_link:
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.).
charter_link: charter.md
label: storage
leadership:
chairs:
Expand Down