Skip to content

Commit 3ef9c2c

Browse files
authored
Merge pull request #7190 from xing-yang/dp-wg-report-2022
Data Protection WG 2022 Annual Report
2 parents 2c2660e + 6987f1d commit 3ef9c2c

File tree

1 file changed

+26
-25
lines changed

1 file changed

+26
-25
lines changed

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

Lines changed: 26 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -5,56 +5,57 @@
55
1. What work did the WG do this year that should be highlighted?
66
For example, artifacts, reports, white papers produced this year.
77

8-
-
9-
-
10-
-
8+
- KEPs being worked on:
9+
- Restrict volume mode conversion to fix security issue moved to Alpha in 1.24: https://kubernetes.io/blog/2022/05/18/prevent-unauthorised-volume-mode-conversion-alpha/
10+
- Volume Populator moved to Beta in 1.24: https://kubernetes.io/blog/2022/05/16/volume-populators-beta/
11+
- Object Storage API (COSI) moved Alpha in 1.25: https://kubernetes.io/blog/2022/09/02/cosi-kubernetes-object-storage-management/
12+
- Volume Group KEP was being reviewed: https://github.com/kubernetes/enhancements/pull/1551
13+
- Changed Block Tracking KEP was submitted and being reviewed: https://github.com/kubernetes/enhancements/pull/3367
1114

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

14-
-
15-
-
16-
-
17+
We discussed the following topics in addition to KEPs:
18+
- VolumeSnapshot v1beta1 removal discussion: https://docs.google.com/document/d/15tLCV3csvjHbKb16DVk-mfUmFry_Rlwo-2uG6KNGsfw/edit#heading=h.qb01pf8tp27
19+
- Volume replication: https://docs.google.com/document/d/15tLCV3csvjHbKb16DVk-mfUmFry_Rlwo-2uG6KNGsfw/edit#heading=h.6luxmtw9ljkm
1720

1821
## Project health
1922

2023
1. What's the current roadmap until completion of the working group?
2124

22-
-
23-
-
24-
-
25+
- 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 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.
2526

2627
2. Does the group have contributors from multiple companies/affiliations?
2728

28-
-
29+
- 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.
2930

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

33-
-
34-
-
34+
- There were a couple of end users who participated in the meeting.
35+
- 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.
3536

3637
## Membership
3738

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):
39+
- Primary slack channel member count: 247
40+
- Primary mailing list member count: 208
41+
- Primary meeting attendee count (estimated, if needed): 10
42+
- Primary meeting participant count (estimated, if needed): 10
4243

4344
Include any other ways you measure group membership
4445

4546
## Operational
4647

4748
Operational tasks in [wg-governance.md]:
4849

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 2022 are linked from [README.md] and updated/uploaded if needed
52-
- [ ] Updates provided to sponsoring SIGs in 2022
53-
- [$sig-name](https://git.k8s.io/community/$sig-id/)
54-
- links to email, meeting notes, slides, or recordings, etc
55-
- [$sig-name](https://git.k8s.io/community/$sig-id/)
56-
- links to email, meeting notes, slides, or recordings, etc
57-
-
50+
- [x] [README.md] reviewed for accuracy and updated if needed
51+
- [x] WG leaders in [sigs.yaml] are accurate and active, and updated if needed
52+
- [x] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed
53+
- [x] Updates provided to sponsoring SIGs in 2022
54+
- [sig-storage](https://git.k8s.io/community/sig-storage)
55+
- 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=111388712
56+
- KubeCon Updates:
57+
- Data Protection WG Deep Dive at KubeCon North America 2022: https://sched.co/182MZ
58+
- Data Protection WG Deep Dive at KubeCon Europe 2022: https://sched.co/ytnj
5859

5960
[wg-governance.md]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md
6061
[README.md]: https://git.k8s.io/community/wg-data-protection/README.md

0 commit comments

Comments
 (0)