Kubernetes Data Protection Working Group, 26 Jan 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes SIG Storage - Data Protection Workgroup Bi-Weekly Meeting 20220126

Description

Kubernetes Data Protection Workgroup Bi-Weekly Meeting - 26 January 2022

Meeting Notes/Agenda: -

Find out more about the Data Protection WG here: https://github.com/kubernetes/community/blob/master/wg-data-protection/data-protection-workflows-white-paper.md

Moderator: Xing Yang (VMware)

A

Hello, everyone today is january, 25th 2022. This is the kubernetes data protection wahing group meeting today we don't have big items on the agenda, so we'll do some updates.

A

First thing is that the our white paper is finally merged, so you can take a look. I think there are. I need to do some format changes. I submitted a small pr to update those. uh So thank thanks. Everyone who have contributed to this white paper so added the the link here. You can take a look.

B

Great thanks, everyone.

A

A

And uh and then we have some caps that we are working on in one.check for the 1.24 release, so the first one is this body mode conversion cap. We discussed this a few times in this meeting. So now there is a. There is a cap that is submitted. It's been reviewed so.

A

Yeah you're welcome to take a look, and please add your comments if you're reviewing them and so yeah has been reviewing it and also uh I pinned the uh jordan to take another to take a look. He said he is an api review and also uh he's attack leading the uh in sick off.

A

So, let's see what he says about this uh cap.

C

Yeah, we also talked about uh like uh what the I mean scenarios where the conversion may be needed, like in future, with cbt.

C

So that I'm guessing this is uh for the case where you want to there's another one.

A

This crap did you, have you heard, have you got a chance to so maybe.

C

I haven't reviewed it.

A

Oh yeah, if you can do so, maybe that's the use case right. So in the use case section um I think maybe we need to clarify that. So I think so ronald is working on this cup. We did. uh There is a there is a well. Maybe it's easier to to see this. Otherwise it's a little hard to see all right right. So there's a.

A

So we talked about uh the motivation, but this is uh you know how how we uh find out this. There could be a problem right. So this is a automotive conversion. If you there's some malicious user write some data like this and then potentially it could be even the cv, and then we talked about the goals goes just to mitigate the vulnerability.

A

Non-Goals is this is another generic way of solving all the problems as what we were trying to do initially using the uh security standard or something right. So this is specific for this problem, so the proposal and then there's okay. So this may be the section that you can maybe comment and yeah. I think we didn't mention cvt. Maybe that's a good point. We should add uh so this story, one.

A

uh This is a kind of talking in there they're generally just saying that back vendors may want may need to convert it.

A

So, basically, just to take a look of the world international content, then that should have a that should have the information of the the original voting mode and then um and then compare that with and then looking at that and then come up with a new mode and then also notice this annotation that will be added by the backup software on the uh on the content to say, allow what you want to come come allow one more change.

A

If that is there, and then that is allowed, so the so the default. So this is like a new restriction right. So if it's, if you didn't add anything, then we have to support blackboard compatibility. So it's it just works the same way. Today at least that's normally the case since what ad industry knew um so that maybe the use case, we should add that we also need this to support cbt.

C

Yeah, so cb2 would be a valid case where this conversion is needed.

A

Okay, so we can add it, uh we can add it here. Can we go back go back to here, just I can just add it now.

D

But seeing that the funny thing is it works today and we're trying to make it work less of the time right. I.

A

Know but that, but I mean that I don't know, I don't know how to change it. That's the we have to support a backward compatibility right. So that's the thing you're, adding a new field there. So yeah, that's how it's about.

D

But I mean change: block tracking is not dependent on this. It's just change.

A

D

Tracking is dependent on this, not breaking backwards. Compatibility.

A

Okay, so yeah, what do you want to do? Do we need to add anything about cbt or no.

C

So I mean uh so what I wanted point here was like in case of cpt. Obviously, if it's a file system pb uh and on a block storage, so we would do cbt right and but then, when we restore, we will restore a block pv and then convert to file system. So.

A

Yeah we want to so it's what uh I think he didn't uh write the entire workflow. Basically, I think he, this is only part of the backup when you're doing this needed. So do we want to elaborate more. Do you think that we can yeah.

C

We can comment, I guess then yeah.

A

Yeah, do you want to? Maybe it's a it's good for you to also comment on this? I think I actually, I did add something here. I think or not- maybe not this one, and there was some some place where I actually asked him to saying that this is a part of the backup process. So this is uh yes, please so feel free to to add your comments there. So you know how you want him to rephrase this to make this more clear.

A

This is right. Now it's really just like a section of that whole thing didn't talk about how the whole backup restore process works. Just talking about, there's a need to do this conversion yeah. We can highlight.

C

Those okay: what plays use cases.

A

Okay, thank you yeah. So, basically, right now there are the first use cases. This is really for the backup use case and the second one is the this. Is the you know the the malicious user case, then how this can help prevent that from happening?

A

uh Yeah, that's meaning it right. Basically, this one we uh this one. We talked about last time that we need to. This is one api change. We need to add this, so the thing is this: one has to be a.

A

uh We need to allow this one to be uh new, because uh you know just to put backup commodity. So that's the that's the thing it's a little weird um and then the annotation it's the second part.

A

Yeah, please uh add comments I'll just add here. Please comment this.

A

Pr so the deadline- um I should add here.

A

That line so the cap, which that line is.

A

It's about a week away, let's see if we can make it.

A

Any other comments about the cap yeah the place uh do review it make sure that works for you.

A

And voting populator, then you want to give an update on the voting populator.

D

um I don't have much of an update, I mean uh we uh we intended to take the feature to beta in the last release, and it didn't happen just because I didn't get my metrics changes done emerged in time, but um that is one of those metric exchanges is ready and the other one is almost ready for 124 and that's those are the that and better testing are the main requirements to go to beta.

D

So, um and I I guess I'll also mention that um we've become aware of more and more people building features based on. You know: data populators. You know different types of data sources for different types of use cases, so it's certainly uh tapping into a real real need. um Yeah.

A

I actually I need it. Yeah.

D

Yeah so I mean it.

A

A

Do you have a do? You have a cap, you need? Oh, uh you actually have everything you passed prior.

D

Already right, you don't.

A

D

I I need to update my cap with new version numbers, but that's just to pro forma change and and then we just need to finish the work um and get it reviewed um and that that's totally on me. So, yes, I I'm splitting my time between that work and other things, and it didn't get as much time as it needed in the last cycle. So I'm really focused on making sure it gets done early this time around.

A

Okay, yeah, it's mainly the the entry one that deadlines come in. I think, that's march, sometime in march, maybe end of march yeah code march, downline right that that's the one you need to make.

A

Okay, all right thanks uh other clubs, I think the unfortunately the content notifier, I think chanting and I and I have not made much progress because we still need to uh get folks in seek node to agree to it and then there's also some api side comments that we still need to get addressed so uh yeah, so that one is not going to make it.

A

um I think that's all for the cap updates.

A

And oh and cbt uh think uh finally, you said you will have some time to work on the design right. You'll continue to work on the design is the phone here.

E

I'm here, but I I haven't, had a chance to work on it. Yet: okay,.

A

But do you plan to continue to work on the design in 1.24.

E

A

Okay, thank you, okay, so uh there is a issue uh I forgot who brought this up last time and is he here? I brought this up yeah, I'm.

F

A

Oh, I'm sorry what uh what is your? What what's your name? Oh okay,.

A

This one see right: okay, uh yeah, so that one we actually, we actually have a pr out. So it's something that is easy for you to reproduce.

F

uh I think uh the person who sent the pr already did some testing around it. uh I didn't get a chance yet. uh Okay,.

A

If you can yeah I'd I'd like another person to also test his fix before we get that merged, uh you know if you, if this is something that is easy for you to reproduce. I mean it'll be great. If you can also test, ah it was slightly.

F

Difficult for me, honestly, like I'm, not oh.

A

F

Not really used to it, yeah.

A

Never mind that I'll see if it was it, because that one was let's see who opened this one like.

F

15 hours ago,.

A

I saw somebody else: oh okay, but no it's not. I thought there's another person all right, okay, yeah, so it sounds like uh yeah. Definitely that the fix looks promising. um Basically, what happens is so do you guys only see this problem? If there is a let's say, there's a failure. Just always fails right. That's the only time because, uh um let's see how did he, how did he you see how he reproduced this okay? I need to take a look and see how to reproduce this issue.

A

I think it's just need to keep something that is: uh okay now use this okay, so if you give a non-existing volume, this will always be. uh This will always fail anyway, but then there's no.

A

So I guess I want to find out is: is this the only time that we are seeing this constantly or are there other times that we're missing? I guess that's the only thing that I want to find out so the fix he made. I think it definitely makes sense. Basically he just uh um what did he do he basically basically just say we don't we we basically don't process it.

A

If we are seeing this, uh uh the update is trying to remove this uh when we snapshot being created, annotation and then in this case we don't. We don't try to you know if we process it again, you're going to get another chris snap shot call which we want to. uh We want to uh skip right, so we don't want to do that. uh So it makes sense, but I just want to know if, like there are other, is this only case that we see this this.

F

Experience we were only able to reproduce this one particular scenario, others. I am personally not aware.

A

Okay, so maybe this is yes seems uh reasonable- the fix, oh I'll, just receive news and that someone else can also try this one out, but otherwise that seems to be fine awesome. Okay, thanks for this thanks, hey! Thank you!

A

um That's all I have here today, so we don't have a lot in today's agenda uh anything else. Anyone want to bring up today.

F

So when will the white paper get published.

A

This is already published, oh.

F

It's published right already, so if.

A

You look at okay. Let me show you so if you click this, so if you see this, it's here right here, this link is already. This is a so. This is a github.

G

Okay, here, yes, it's.

A

Already public right, so this link is already public.

A

So this is, this is not a blog. This is a this is basically, we have our own repo here under this right. So, but this document is already public.

A

B

Update for this.

A

B

Do you envision any updates like? Should we open pr.

A

Yeah, if you want to update, definitely you can open prs and you know and there's also so so I think I did open a small pr because there's some, I think some small changes. I think shantae added some comments, but I didn't get a chance to uh uh fix it before it got merged. So I do have a small pr out. Let's see, let you have it here.

A

Right so I do have so so this is a small, very small one. Just so there are some formatting changes, basically very small changes to this. So uh if there is anything else, you think we should add to the to the paper yeah, you can feel free to submit a pr or something yeah.

B

Excellent. Thank you.

A

Yeah, thank you.

B

Can I ask how um allison was a reviewer on that? Did you ask.

A

Okay, I'm sorry, your volume is a little low. Sorry, one second.

A

uh Ben, do can you add your cap here there's a question for relevant link for this voting populator.

B

um Yeah I can, uh I can find the link. Okay, thanks did you? um Do you add allison to that pr request, or was that automatically added.

A

Which? Which pr.

B

The pr to update the white paper doc.

A

B

A

Did I add what.

B

uh Allison as a reviewer.

A

I did not, this is automatic. I think.

B

Oh wow, okay, so.

A

This is so yeah, so whenever you submit up here, because this is a community repo right yeah because she is, uh I think she works in the community right she's only in some owner file, so it will automatically pick some reviewers yeah great yeah. So I just so. I just assigned this to shenzhen, but you know you can assign this to anybody or add. Maybe not I don't know how to add reviewers here, but you can assign this to to other people that you want. If you want anyone to review this yeah, I don't yeah.

A

I think yeah. Definitely this. These two reviewers are added automatically because she is already a owner somewhere here. The community ripple yeah.

G

Excellent. Thank you. Okay,.

A

A

Okay, uh do we have anything else.

A

All right, then, that's it for today thanks everyone. Thank you.

B

A

B