Skip to content

Commit 1f386ea

Browse files
authored
Merge pull request #6569 from xing-yang/report_dp_wg_2021
DP WG annual report 2021
2 parents 3b21eda + f98045f commit 1f386ea

File tree

1 file changed

+37
-23
lines changed

1 file changed

+37
-23
lines changed

wg-data-protection/annual-report-2021.md

Lines changed: 37 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -1,62 +1,76 @@
11
# 2021 Annual Report: WG Data Protection
22

3+
Note: Only include KEPs targeting 1.21, 1.22, and 1.23 releases.
4+
35
## Current initiatives
46

57
1. What work did the WG do this year that should be highlighted?
68
For example, artifacts, reports, white papers produced this year.
79

8-
-
9-
-
10-
-
10+
- [Data Protection White Paper](https://github.com/kubernetes/community/blob/master/wg-data-protection/data-protection-workflows-white-paper.md)
11+
- KEPs being worked on:
12+
- Restrict volume mode conversion to fix security issue: Had discussions in the WG and submitted KEP to introduce it as an Alpha feature: https://github.com/kubernetes/enhancements/pull/3151
13+
- Working on moving Volume Populator to Beta: https://github.com/kubernetes/enhancements/pull/2934
14+
- Object Storage API (COSI): KEP is being updated and reviewed: https://github.com/kubernetes/enhancements/pull/2813
15+
- ContainerNotifier KEP review in progress: https://github.com/kubernetes/enhancements/pull/1995/
16+
- Volume Group KEP review in progress: https://github.com/kubernetes/enhancements/pull/1551
1117

1218
2. What initiatives are you working on that aren't being tracked in KEPs?
1319

14-
-
15-
-
16-
-
20+
We discussed the following topics in the WG that are not tracked in KEPs:
21+
- Change Block Tracking (CBT) API design: https://docs.google.com/document/d/15tLCV3csvjHbKb16DVk-mfUmFry_Rlwo-2uG6KNGsfw/edit#heading=h.1olwavha9frv
22+
- Volume Replication: https://docs.google.com/document/d/15tLCV3csvjHbKb16DVk-mfUmFry_Rlwo-2uG6KNGsfw/edit#heading=h.pah3yke9ddug
23+
- Backup and restore externally managed services:
24+
- https://docs.google.com/document/d/15tLCV3csvjHbKb16DVk-mfUmFry_Rlwo-2uG6KNGsfw/edit#heading=h.7zwanijz69u1
25+
- https://docs.google.com/presentation/d/1IM6d0w3CDdHv1dLaFNXEcxy5fuDTr9LERAdMVkZiK9s/edit#slide=id.p
26+
- Snapshot policy (immutable snapshot): https://docs.google.com/document/d/15tLCV3csvjHbKb16DVk-mfUmFry_Rlwo-2uG6KNGsfw/edit#heading=h.gb8m7t8jro1v
27+
- Securing S3 Backups against Ransomware: https://sched.co/igUT
28+
- Volume Snapshot GA phases: https://docs.google.com/document/d/15tLCV3csvjHbKb16DVk-mfUmFry_Rlwo-2uG6KNGsfw/edit#heading=h.w8v8tpkuw8ac
29+
- Kubernetes Data Protection with Velero: https://docs.google.com/document/d/15tLCV3csvjHbKb16DVk-mfUmFry_Rlwo-2uG6KNGsfw/edit#heading=h.iekhl8nl58lo
1730

1831
## Project health
1932

2033
1. What's the current roadmap until completion of the working group?
2134

22-
-
23-
-
24-
-
35+
We have identified the missing building blocks for supporting Data Protection in Kubernetes in our white paper: https://github.com/kubernetes/community/blob/master/wg-data-protection/data-protection-workflows-white-paper.md#what-are-the-missing-building-blocks-in-kubernetes. Features such as Volume Backups, Change Block Tracking, Volume Populator, Volume Group and Group Snapshot, and Backup Repositories are owned by SIG Storage. Features such as Quiesce and Unquiesce Hooks are owned by SIG Node, with SIG Storage and SIG Apps participating. Features such as Application Snapshots and Backups are owned by SIG Apps, with SIG Storage participating. We will continue to work on them until all the missing pieces are available in Kubernetes.
2536

2637
2. Does the group have contributors from multiple companies/affiliations?
2738

28-
-
39+
Yes. In our [agenda doc](https://docs.google.com/document/d/15tLCV3csvjHbKb16DVk-mfUmFry_Rlwo-2uG6KNGsfw/edit#), we listed companies who are supporting the WG. Here are some of the companies that actively participating in the WG: Cohesity, Dell EMC, Druva, Google, Infinidat, Kasten by Veeam, Microsoft, Mirantis, NetApp, Red Hat, Seagate, Trilio, Veritas, and VMware.
2940

3041
3. Are there ways end users/companies can contribute that they currently are not?
3142
If one of those ways is more full time support, what would they work on and why?
3243

33-
-
34-
-
44+
- There were a couple of end users who participated in the meeting and brought up topics such as how to backup and restore externally managed services.
45+
- If more end users/companies can attend our meetings, provide feedback, and contribute to design/implementation of the features we are working on, that will be great.
3546

3647
## Membership
3748

38-
- Primary slack channel member count:
39-
- Primary mailing list member count:
40-
- Primary meeting attendee count (estimated, if needed):
41-
- Primary meeting participant count (estimated, if needed):
49+
- Primary slack channel member count: 196
50+
- Primary mailing list member count: 193
51+
- Primary meeting attendee count (estimated, if needed): 25
52+
- Primary meeting participant count (estimated, if needed): 25
4253

4354
Include any other ways you measure group membership
4455

4556
## Operational
4657

4758
Operational tasks in [wg-governance.md]:
4859

49-
- [ ] [README.md] reviewed for accuracy and updated if needed
50-
- [ ] WG leaders in [sigs.yaml] are accurate and active, and updated if needed
51-
- [ ] Meeting notes and recordings for 2021 are linked from [README.md] and updated/uploaded if needed
52-
- [ ] Updates provided to sponsoring SIGs in 2021
53-
- [$sig-name](https://git.k8s.io/community/$sig-id/)
60+
- [x] [README.md] reviewed for accuracy and updated if needed
61+
- [x] WG leaders in [sigs.yaml] are accurate and active, and updated if needed
62+
- [x] Meeting notes and recordings for 2021 are linked from [README.md] and updated/uploaded if needed
63+
- [x] Updates provided to sponsoring SIGs in 2021
64+
- [sig-storage](https://git.k8s.io/community/sig-storage)
5465
- links to email, meeting notes, slides, or recordings, etc
66+
- WG does not own code. We discussed the features such as CBT, Volume Populator in the WG meeting, but we still get the features tracked in SIG Storage and they are in the tracking spreadsheet. This means we’ll give an update on them in every SIG Storage bi-weekly meeting: https://docs.google.com/spreadsheets/d/1t4z5DYKjX2ZDlkTpCnp18icRAQqOE85C1T1r2gqJVck/edit#gid=705655608
5567
- [$sig-name](https://git.k8s.io/community/$sig-id/)
5668
- links to email, meeting notes, slides, or recordings, etc
57-
-
69+
- KubeCon updates
70+
- KubeCon Europe 2021: https://www.youtube.com/watch?v=DBxOBzBkimo
71+
- KubeCon NA 2021: https://www.youtube.com/watch?v=pTDWiHmpEz8&t=4s
72+
- KubeCon China 2021: https://www.youtube.com/watch?v=rHRhmi76Q4I
5873

5974
[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md
6075
[README.md]: https://git.k8s.io/community/wg-data-protection/README.md
6176
[sigs.yaml]: https://git.k8s.io/community/sigs.yaml
62-

0 commit comments

Comments
 (0)