Kubernetes Data Protection Working Group, 6 Apr 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes Data Protection WG Bi-Weekly Meeting 2022-04-06

Description

Kubernetes Data Protection WG Bi-Weekly Meeting - 06 April 2022

Meeting Notes/Agenda: -

Find out more about the DP WG here: https://github.com/kubernetes/community/tree/master/wg-data-protection

Moderator: Xiangqian Yu (Google)

A

B

This meeting is being recorded.

A

Yeah hello: everyone today is april 6 uh 2022. This is a data protection working group in kubernetes. um We don't have too much agenda today. uh The cup of uh cape updates will just quickly go through if there's anything new there, and then we will open the discussion to the group. If there's any discussion, uh we can continue. Otherwise we will just return um half an hour or something to the to the group over here.

A

Let's first go through the uh cape of this william populator. I think it's is any anything new from that side. Ben soon,.

C

uh So the uh the update from alpha to beta did merge in the 124 by the 124 feature. Freeze date, we got tests, we got docs so um that it's going to beta. We have all the releases done. We just. I just need to write a blog about it.

A

You uh did, I lost your voice, so I just you're done hey. Can you hear.

D

A

Yeah now I can hear you you were talking.

C

A

And that's it we will. I I lost the remaining yes.

C

Oh no, that was the last thing I said was I I need to uh there's going to be a a beta blog that will update the blog that will describe how to use the feature now with the updates since alpha, but and that hasn't been written yet. But everything else is done for this cycle.

A

Nice huge congratulations.

C

D

C

A lot of help from other people in the community. It wasn't just.

D

Me I know, but it's a group work for sure, but just a lot of work, yeah great job, yeah.

A

Okay uh volume mode convention: this is for shin action.

B

Yeah uh ronak is the one who's working on this he's, probably not in the meeting uh yeah. So uh it's going on well, since that code is all auto tree, so we are not limited by the entry code freeze deadline, um so I think we will need to cut another rc release from excellent snapshotter and after that, we'll just continue to update the changes to xml provisioner uh yeah. So so uh I think things are on track and the results there will be a blog as well.

A

Sounds good. This is also targeting 1.22.

B

A

B

No, this is one point, twenty four. So basically the outer tree thing we normally cut outside cars after the kubernetes piece, so it's 1.24 as well alpha, two four, okay! So, basically right now it's a working progress.

A

A

Thank you, uh uh causey.

B

So I think cozy side of the the cap is still uh being reviewed. There are back and forth. I see that sits, just updated the cap yesterday, so yeah still being reviewed.

C

What is the, what is the next milestone with cozy, so that I think.

B

It has to be 1.25, it's too late, 1.24.

C

Right, but what I mean is is, as after we get all the the spec issues sorted out and agreed to and merged like then, what.

B

Then we need to update all the implementation right, so we actually already.

C

B

Implementation, but it's based on the old old cap so now.

A

We just need to update.

B

All of those yeah, I think it's just once: okay.

C

And in principle that could happen as part of like the kubernetes 125 release. That's what you're saying.

B

Right right, because right now, it's way too late for 1.24. It's it's going to get the cap is not it not a year. It's not just too way too late. I know this is our tree, but still so.

A

Even 1.24 or 5 may not necessarily be realistic.

B

uh Well now 25 it's possible because once the cap is in, then we just need to update the indentation, which should be quick, relatively quick.

A

Yeah, but the key is that the windows I'm.

C

Trying to understand that the best case like I realize things can always slip, I'm just trying to get them right. The.

B

Best is 1.25 yeah. What what do you mean vendor? I'm not getting what you're trying to say.

A

Kodzi needs to the uh the object storage windows to be able to provide the interfaces right in order for.

B

It's already yeah, there's already interfaces right. It's just need to be agreed on the the cab has those interfaces it has both kubernetes apis and also the grpc interfaces. You just need to get that merge and then implement that, and I mean there are already implementation, just need to update the invitation based on the updated design, and there is a also there is a the sample driver right then. What is that, as a sample driver? I think we removed the.

D

A

For uh s3 and the gcs.

B

uh I think the sample driver is a different. It's not really s3, it's just an example. I believe. Do you remember, because initially I think there was a menial driver, but then I think because the license changed so that one is no longer there. uh We archived that I think there was a sample driver. uh I forgot exactly what is that just right into a file ben? Do you remember what that sample driver? Do I don't remember? I.

C

I don't remember, I remember the minion driver getting removed. I know that, like netapp did a poc with the old alpha and our implementation, and so like as soon as there's a new implementation. We'll update our pfc but like turning that into a shipping product is still a lot of steps to go.

B

Yeah, but good thing is, there are actually a lot of vendors are already doing some poc with it. You know, uh grant on footworks he's. He also has done a poc just based on sample driver, so yeah so just need to get the cap merged. First.

A

Oh anyways, uh this is say hopefully 41.25.

E

Okay, juan yeah.

A

E

Just give a quick update because we haven't got much progress so far on the prototype. We need to do some more research to see which apis uh woodwood vendor that have an api for us available for us to play around with, and we need to do some experiment before we can go update prototype. So that is the short update for on outside.

E

We try to have a meeting among the people who are involved in this project every week on thursday afternoon uh pacific time uh last week we have it on uh at 6 00 p.m. But this week a few members of our team request to move it up one hour, so we will have it at 5 p.m. I will post, uh I will post the the information about the meeting on slack.

E

So if you are, if you are interested you can, you know, follow us on slack for the channel for the data protection to get more detail.

B

If you have all the midi notes in the same dock, right.

E

Yeah yeah all the meetings. Okay,.

B

Thank you for capturing the.

E

Notes, that's very helpful.

E

Yeah I mean I I capture all of the notes and if you don't want to attend a meeting, you can just read the note to get the gut of what's going.

A

A

Cool sounds good.

A

Okay, uh the the any open issues she and I saw you put one over there. What could come yo? You will be there now.

B

Oh good yeah, so uh I will be there yeah I'll, be there in person. You're saying you will be no.

A

B

Virtually right, okay, all right, yeah and make it okay yeah. So we will have a session. So it's going to be a worksheet session for the data protection group, uh a tom you added there right. You will be there. Yeah uh we've a bunch of people.

C

B

Wondering if we want to do it face to face or anything like that.

B

It doesn't meet up, so, let's see so I'll, be there I'll say in person.

B

So, who else will be there in person.

A

Oh I'll, be there as well, my name is ivan, I'm so can you write.

B

Down your name sure.

E

It's probably these are people who are going in another name here.

B

Yeah, just yeah, please right right on yourself.

E

Is there a sig storage face to face too.

B

No, they won't be because uh uh sad michelle, they are not going there so, but.

C

B

Myself and young will be there. We have a sick storage deep dive session, so that session will be in person.

B

uh Weekend so so there is a, I wonder there will be a contributor um meet up on monday.

B

uh There. Usually there will be some tables there. I wonder if we could just uh gather there if that makes sense or treated with later. Will everybody be there on monday, though, I guess that's another question.

C

I'll be there monday, I'm happy to man a table if we would like that sure.

B

Yeah I can, I can ask the the so I know last time uh I I just see there there or some information about this contributor summit. They say it's going to be similar to last time. uh Last time. It's just a pretty. I think it's a kind of a quiet event. They don't really have any formal agenda going on. Just there are some tables. So so you can just grab a table and see there.

B

So we could yeah, we could do that. I can yeah. Let me ask those people.

C

Yeah that'd be great.

B

Let's see say monday.

B

Let's leave the school meet up.

E

I'll be um arriving around noon.

A

On monday, so maybe.

B

We could do that yeah. We could try to arrange them in the afternoon. Sure.

A

Yeah yeah or I can just being calm and try to find out where everyone is yeah. Don't don't worry about me? Thank you.

C

Yeah we'll be pretty jealous at that point, probably.

B

Yeah so uh yeah, so I just uh last time I remember it's pretty. You know a lot of a lot of empty tables. This time I assume there'll be more people attending than last time in north america yeah. It's response last time.

A

All right cool we can leave this to slack channel. I think it's a good idea to meet face to face. uh I miss the days where I can go there as well.

B

You can set up something for you to join virtually a little bit. I think the time zone will be.

A

Yeah, you don't get the human touch from it. Yeah.

B

It's different also, I think it's going to be like a pretty big room, so it's pretty hard yep.

A

All right, cool anything else join the group.

A

All right return, 40 minutes actually to you today. Thanks thanks. Everyone thanks. Everybody cheers.