Data Protection Working Group

OWNERS_ALIASES

@@ -103,6 +103,9 @@ aliases:
     - mtaufen
     - stealthybox
     - sttts
+  wg-data-protection-leads:
+    - xing-yang
+    - yuxiangqian
   wg-iot-edge-leads:
     - cantbewong
     - cindyxing

sig-list.md

@@ -53,6 +53,7 @@ When the need arises, a [new SIG can be created](sig-wg-lifecycle.md)
 |------|------------------|-----------|---------|----------|
 |[Apply](wg-apply/README.md)|* API Machinery<br>* CLI<br>|* [Daniel Smith](https://github.com/lavalamp), Google<br>|* [Slack](https://kubernetes.slack.com/messages/wg-apply)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-apply)|* Regular WG Meeting: [Tuesdays at 9:30 PT (Pacific Time) (biweekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
 |[Component Standard](wg-component-standard/README.md)|* API Machinery<br>* Architecture<br>* Cluster Lifecycle<br>|* [Michael Taufen](https://github.com/mtaufen), Google<br>* [Leigh Capili](https://github.com/stealthybox), Weaveworks<br>* [Dr. Stefan Schimanski](https://github.com/sttts), Red Hat<br>|* [Slack](https://kubernetes.slack.com/messages/wg-component-standard)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-component-standard)|* Regular WG Meeting (please join [email protected] or [email protected] to access the notes): [Tuesdays at 08:30 PT (Pacific Time) (weekly)](https://zoom.us/j/705540322)<br>
+|[Data Protection](wg-data-protection/README.md)|* Apps<br>* Storage<br>|* [Xing Yang](https://github.com/xing-yang), VMware<br>* [Xiangqian Yu](https://github.com/yuxiangqian), Google<br>|* [Slack](https://kubernetes.slack.com/messages/wg-data-protection)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-data-protection)|* Regular WG Meeting: [Mondays at 9:00 PT (Pacific Time) (bi-weekly)](https://docs.google.com/document/d/15tLCV3csvjHbKb16DVk-mfUmFry_Rlwo-2uG6KNGsfw/edit)<br>
 |[IoT Edge](wg-iot-edge/README.md)|* Multicluster<br>* Network<br>|* [Steve Wong](https://github.com/cantbewong), VMware<br>* [Cindy Xing](https://github.com/cindyxing), Microsoft<br>* [Dejan Bosanac](https://github.com/dejanb), Red Hat<br>* [Preston Holmes](https://github.com/ptone), Google<br>|* [Slack](https://kubernetes.slack.com/messages/wg-iot-edge)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-iot-edge)|* APAC WG Meeting: [Wednesdays at 5:00 UTC (every four weeks)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>* Regular WG Meeting: [Wednesdays at 09:00 (Pacific Time) PT (every four weeks)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
 |[K8s Infra](wg-k8s-infra/README.md)|* Architecture<br>* Contributor Experience<br>* Release<br>* Testing<br>|* [Bart Smykla](https://github.com/bartsmykla), VMware<br>* [Davanum Srinivas](https://github.com/dims), VMware<br>* [Aaron Crickenberger](https://github.com/spiffxp), Google<br>|* [Slack](https://kubernetes.slack.com/messages/wg-k8s-infra)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-k8s-infra)|* Regular WG Meeting: [Wednesdays at 8:30 PT (Pacific Time) (bi-weekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>
 |[LTS](wg-lts/README.md)|* API Machinery<br>* CLI<br>* Node<br>|* [Dhawal Yogesh Bhanusali](https://github.com/imkin), VMware<br>* [Quinton Hoole](https://github.com/quinton-hoole), Huawei<br>* [Tim Pepper](https://github.com/tpepper), VMware<br>* [Nick Young](https://github.com/youngnick), VMWare<br>|* [Slack](https://kubernetes.slack.com/messages/wg-lts)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-lts)|* Regular WG Meeting: [Tuesdays at 09:00 PT (Pacific Time) (bi-weekly)](https://docs.google.com/document/d/1FQx0BPlkkl1Bn0c9ocVBxYIKojpmrS1CFP5h0DI68AE/edit)<br>

sigs.yaml

@@ -2306,6 +2306,39 @@ workinggroups:
     teams:
     - name: wg-component-standard
       description: Component Standard Discussion
+- dir: wg-data-protection
+  name: Data Protection
+  mission_statement: >
+    A Working Group dedicated to promoting data protection support in Kubernetes,
+    identifying missing functionality and working together to design features to enable
+    data protection support. Involves collaboration with multiple SIGs such as Apps
+    and Storage.
+
+  charter_link: charter.md
+  stakeholder_sigs:
+  - Apps
+  - Storage
+  label: data-protection
+  leadership:
+    chairs:
+    - github: xing-yang
+      name: Xing Yang
+      company: VMware
+    - github: yuxiangqian
+      name: Xiangqian Yu
+      company: Google
+  meetings:
+  - description: Regular WG Meeting
+    day: Monday
+    time: "9:00"
+    tz: PT (Pacific Time)
+    frequency: bi-weekly
+    url: https://docs.google.com/document/d/15tLCV3csvjHbKb16DVk-mfUmFry_Rlwo-2uG6KNGsfw/edit
+    archive_url: http://bit.ly/wg-data-protection-notes
+    recordings_url: http://bit.ly/data-protection-playlist
+  contact:
+    slack: wg-data-protection
+    mailing_list: https://groups.google.com/forum/#!forum/kubernetes-data-protection
 - dir: wg-iot-edge
   name: IoT Edge
   mission_statement: >

wg-data-protection/README.md

@@ -0,0 +1,35 @@
+<!---
+This is an autogenerated file!
+
+Please do not edit this file directly, but instead make changes to the
+sigs.yaml file in the project root.
+
+To understand how this file is generated, see https://git.k8s.io/community/generator/README.md
+--->
+# Data Protection Working Group
+
+A Working Group dedicated to promoting data protection support in Kubernetes, identifying missing functionality and working together to design features to enable data protection support. Involves collaboration with multiple SIGs such as Apps and Storage.
+
+The [charter](charter.md) defines the scope and governance of the Data Protection Working Group.
+
+## Stakeholder SIGs
+* SIG Apps
+* SIG Storage
+
+## Meetings
+* Regular WG Meeting: [Mondays at 9:00 PT (Pacific Time)](https://docs.google.com/document/d/15tLCV3csvjHbKb16DVk-mfUmFry_Rlwo-2uG6KNGsfw/edit) (bi-weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=9:00&tz=PT%20%28Pacific%20Time%29).
+  * [Meeting notes and Agenda](http://bit.ly/wg-data-protection-notes).
+  * [Meeting recordings](http://bit.ly/data-protection-playlist).
+
+## Organizers
+
+* Xing Yang (**[@xing-yang](https://github.com/xing-yang)**), VMware
+* Xiangqian Yu (**[@yuxiangqian](https://github.com/yuxiangqian)**), Google
+
+## Contact
+- Slack: [#wg-data-protection](https://kubernetes.slack.com/messages/wg-data-protection)
+- [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-data-protection)
+- [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/wg%2Fdata-protection)
+<!-- BEGIN CUSTOM CONTENT -->
+
+<!-- END CUSTOM CONTENT -->

wg-data-protection/charter.md

@@ -0,0 +1,80 @@
+# WG Data Protection Charter
+
+This charter adheres to the [wg-governance] guidance as well as
+the general conventions described in the [Kubernetes Charter README] and
+the Roles and Organization Management outlined in [sig-governance], where
+applicable to a Working Group.
+
+
+## Scope
+
+Data protection in Kubernetes context typically involves backup and recovery
+of two types of entities:
+* Kubernetes API object resources
+* Persistent volume data
+We consider it a complicated and layered problem, including backup and recovery
+at persistent volume level, application level, and cluster level. Part of the
+working group’s charter is to define what Kubernetes native constructs are
+required to achieve these goals.
+
+The Data Protection Working Group is organized with the goal of providing
+a cross SIG forum to discuss how to support data protection in Kubernetes,
+identify missing functionality, and work together to design features that
+are needed to achieve the goal.
+
+### In scope
+
+* High level discussions on what it means to support data protection in Kubernetes at different levels and how to do it.
+* Design discussions on specific topics related to data protection and disaster recovery support.
+* Document results of discussions and investigations in a linkable medium.
+
+Potential design topics include, but are not limited to the following:
+* Read data from a snapshot without creating a new volume.
+* Volume backups
+* Data populator
+* Retrieve diffs between two snapshots (block and file level)
+* Consistency volume groups (group snapshot)
+* Application snapshot, backup, and recovery
+* Data protection policy (Data protection policy usually means we can set up a schedule to do
+  periodic backups, set a backup retention policy to automatically clean up old backups, set a
+  topology to specify a backup location, etc. It can also possibly include policies such as
+  `backups must be encrypted` and `secrets must be encrypted at rest and in transit`.)
+* Data protection workflows
+
+### Out of Scope
+
+* Design discussions not related to data protection is out of scope. For example,
+  how to migrate in-tree drivers to CSI drivers and how to report volume health
+  belong to SIG Storage and would not be a focus area of this WG. Workload API designs
+  for StatefulSet and Deployment belong to SIG Apps, however, this WG would be interested
+  in figuring out how to backup and recover a StatefulSet or Deployment.
+* This is a working group so it does not own code. Design discussions for
+  a specific feature including KEP reviews can happen in the working group
+  but KEP approvals and code implementation will be owned by SIG-Apps or
+  SIG-Storage.
+
+
+## Stakeholders
+
+Stakeholders for this working group include members in the following SIGs:
+* SIG Apps
+* SIG Storage
+
+We will also consult SIG Auth from security aspect. Stakeholders also include
+backup vendors who want to provide data protection support in Kubernetes and
+end users who want to use data protection applications.
+
+
+## Disband criteria
+
+This WG will be producing documents as described in the `In Scope` section. If stakeholder SIGs and the WG decide all documents described in the `In Scope` section are complete and no more discussions and investigations are needed in this WG, they may determine to disband this WG.
+
+
+[sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md
+[wg-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/wg-governance.md
+[Kubernetes Charter README]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md
+[lazy consensus]: http://en.osswiki.info/concepts/lazy_consensus
+
+[kubernetes-dev@]: https://groups.google.com/forum/#!forum/kubernetes-dev
+[wg-data-protection@]: https://groups.google.com/forum/#!forum/kubernetes-wg-data-protection
+[kubernetes/k8s.io]: https://git.k8s.io/k8s.io