Kubernetes Storage SIG, 27 Aug 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes SIG Storage - Bi-Weekly Meeting 20200827

Description

Bi-Weekly Meeting of Kubernetes Storage Special-Interest-Group (SIG) - 27 August 2020

Meeting Notes/Agenda: -

Find out more about the Storage SIG here: https://github.com/kubernetes/community/tree/master/sig-storage

Moderator: Xing Yang (VMware)

A

Hello, everyone today is august 27 2020.. This is the kubernetes sixth storage bi-weekly meeting today we will go through 1.20 planning. 1.19 was just released yesterday.

A

A

So this is the spreadsheet copied from the 1.19 spreadsheet, uh so we'll just go over and decide what we are planning to do in 1.1.20, the first one csi online offline resizing volume, expansion fixed issues. uh So I think the plan is to keep the scene beta in 1.20. um So priority is one come on. uh Does this uh look alright,.

B

Yeah, I think it's it's fine.

A

Okay and the next one is recovering from resize failures, uh so we didn't make it in 1.19. So we tried to bring this one to half about 1.20, uh I'm wondering about priority. Should this one be increased because we are saying we want to hold our phone expansion for one more release, I'm hoping to get this one at the alpha feature in 1.20 and then maybe in 1.21, both one those two can one. This one can go beta and then uh williamson pension can go ga. So uh how does this uh priority?

A

B

I think I mean we could keep it as one okay, but I think it's.

A

I'll change 71 then.

A

uh Okay, snapshot yeah. We are trying to bring this to j1.20 um yeah. So I think this one looks good.

A

And next one is now recursive volume on the shape fs group come on. You want to talk about this.

B

Yeah, so the a version of this pr was merged as like implementation was merged as alpha in 118, but 119. We took a step back and considered how a cell and x and fs group both would work together and we have to to rework the cap and I'm working on writing a new cup. So yeah.

A

A

You uh next one is new design for volume file permission handling.

A

Do we get an owner of this one.

A

Looks like we don't have an owner. Does anyone know the status of this pen here.

A

Michelle do you know anything about this one, or would you just leave this one.

C

uh Sorry, what number is that.

A

This is a row number seven yeah new design for volume file permission handling- I don't see an he has owner issue so.

C

Yeah, I don't know if ben's going to have time on that. uh Is anyone interested in working on this? I think the high level item here is uh the volume permissions, how they're handled and kubernetes has kind of been ad hoc and a little bit of a mess, and we wanted to redesign that anybody interested in picking up that design feel free to speak up. If not, we can leave it. Unassigned.

C

A

All right, the next one is file permission handling for windows looks okay, so it looks like deep is working on this uh end of when downloading status has moved to 1.20 okay, so we will just leave it as a design and then probably two is okay.

C

Is uh jing or deep or kk, or anyone from that team on online want to get confirmation.

D

That they're actually going to work on it. This quarter.

E

uh So this is kk. I've not been attending.

D

Those meetings.

E

uh But I've been heard uh discussions around it as well- uh maybe I'll be uh ping in the group and get back to you guys sounds good appreciate.

C

A

Okay, next one is csi. Entry read only handling a humble example here, so it's just moving to 1.20.

A

So we want to move this to ga 1020 priorities too. Does this uh still stay like this or.

C

Let's put a question mark next to humble, I think we need to get.

A

C

If he's gonna be able to work on it or not,.

A

C

Should verify offline.

A

Okay, next, one issues related to assuming volumes are mount points, so this is a black fix. We have nd here. uh So there are looks like there are pr's, I'm going to 1.20 uh any update on this. One would be just keep this as the same priority. 2 bug fix.

A

Let me show you know anything about this. One.

F

Michelle, oh, hey, sorry, um so, yeah there are a couple of pr's out to sort of address various different aspects of this issue. So.

A

F

Expect um we can make progress on this in 120., I'm not sure if we'll be able to fix every single issue, but but I think we can definitely make some progress on it, but yeah. So andy has a big pr out that we had postponed to 120 and then um I think, there's um someone else that has a second pr out. There's two pr's I know of um but there's probably more problems.

F

A

Okay, so is this real priority two and back fix them?

A

Okay, next one storage capacity tracking do we have uh patrick here, so that is so that yeah. So that's a alpha feature in 1.19.

A

uh Do we want to try to move into beta in 1.20 patrick's here or not.

F

Is he here, I think, there's there's quite a bit of feedback that we gave during the alpha design.

E

F

Issues to investigate and resolve by the beta time frame, so I expect patrick will be working on that. I'm not sure if we'll be able to address all of them to move it to beta, but I think we'll be able to make progress towards it.

A

Okay, so we leave it to beta, then priority, two, that this is okay,.

C

Should we target alpha and call it bug fixes for this quarter.

A

Yeah we now the target status will be what bug fixed or still alpha right c.

C

Yeah, let's leave it as alpha that way, we don't uh unnecessarily require, like all the docs work and all these other things that need to happen.

A

A

Next one pvc inline fm volumes, uh so this one is also a new 1019 feature in alpha state. uh So should we try to bring this to beta in 1.20? This is.

F

A

um Patrick's plate: uh do you know anything about this uh michelle saad? Should we keep this like this or are there any.

F

I think I don't recall there being like substantial um design concerns that we need to figure out. There were maybe like two issues that we need to resolve, but um I think it could be feasible target beta in in the 120.

A

Time frame, okay, oh, uh should we also uh look at this one together with this other csi inline volume feature trying to see if we can combine them. Is there something like that? Let's remember seeing something: uh some kind of.

F

That would be a good thing yeah. That would be a good thing to to figure out the the whole api story, uh and if we can consolidate the two features at all into a single.

F

A

A

uh Okay, the next one is a spurring over failure domain, so.

C

Sorry, real quick: can we change uh eventually to now for.

G

Enhancement if.

C

A

A

uh Let's see if there's something else, that we need to change: okay, just this one, all right cool! Thank you, okay, spreading over failure domain, so I think this would still be staying designed um because this uh right now kind of coupled with this uh next uh one warning group api, um so yeah. So this one is still yeah still stays in the uh designs today.

A

If we can actually figure out like if we can actually couple the students who think maybe one can move faster, otherwise, I think there's a lot of issues we need to discuss first, so, uh let's find out, we just keep it design priority. Two, I think that's fine, and next one is a csi, auto 3, more iscsi driver finish. What is this status.

A

uh Michelle, do you know this one, do we do? We have a anyone walking on this already.

F

Oh my scuzzy yeah there were some people that reached out to me that were interested in in helping with the iscsi driver. um I I need to reach back out to them to see if they're still interested um but otherwise, like.

F

I haven't really seen any activity on this repo. Okay,.

G

Michelle this is kidding uh just trying to understand the scope of work here. um What needs to be done.

F

um Yeah so basically, we have the like sort of a common iscsi driver um for csi and we're just looking really looking for an owner um to help drive and maintain the work that needs to be done for this driver. I think right now it like it builds, um but I don't know if anyone's actually tested it.

F

um So, like you know, setting up like the build pipeline and setting up the ci infrastructure for it um and then and then also just sorting through the issues and- and you know seeing what need what work needs to be done.

G

Here I'm currently working on the nfs provisioners setting up the ci and those things. Maybe I can take a look at that part of uh the aspects for this uh csi driver for his qc uh property choice.

F

That would be great.

A

Yeah yeah thank.

A

You next one I see a sci-fi for channel driver duplicate and no this one still has no owner. So we just uh uh we needed.

F

Yeah, I just need to yeah. I just need to hit the button on it to archive this repo. um Okay, I need to get around to doing that.

A

Okay, so looks like it's the same for the next one, see if I flash flex adapter driver okay and next one is the move out glasgow fast provisioner.

A

um So I'm not sure how much work is remaining for this one in progress. This is, uh I think,.

C

Gloucester has already started working on it. He just needs to wrap it up. Okay, so let's leave it aside.

A

And okay, so karen you're working on this next two. um What is this that is for those two is uh still some remaining.

G

uh Line number 19: I think it's a ci related work, that's still pending, uh but I think we have gotten into a motion of uh raising prs and uh the new contributors that are helping uh they're able to review when we are getting for the next line item. There was a cla issue. uh I just before this call. I raised a new pr that fixes it.

G

We will be able to wind that up and we also have a team. Now that is signed up for supporting this, so we should be able to move faster on that as well.

A

Great, thank you. Next one is the volume snapshot name. Space transfer uh is mike still interested working on this.

H

Yeah hi I'm still alive um and interested. Unfortunately, I have no update.

A

Okay, uh so do we still uh so we keep this as a design in 1.20? Is that it looks okay, okay, thanks.

H

A

uh Okay, next is a volume house, so this one is a our feature in 1.19. uh So do we want to bring to beta of thinking?

A

Should we try to um like add those uh one condition to status instead of keeping in as the events in pvc and bring into beta.

A

Michael inside.

C

uh Off the top of my head, I'm not sure let's have the discussion. uh Okay, maybe a couple of design meetings to talk about what we want to do sure we can preliminarily target a beta and then readjust, if needed. Okay, sure.

A

Next one is a generic generic data. Populator is ben online.

I

A

Hi, are you still interested in working on this.

I

Sorry I I like I was in another meeting that.

A

I just joined okay.

I

A

We're looking at the generic data populator, so yeah.

I

We're doing the planning for 120.

A

Okay, yes, yes,.

I

Yeah I mean I I yes, I want to keep working on this um okay, but I don't have visibility into. Is my free time for the next? This guess is four months. We have.

A

I

Yes, but please keep my name on it.

A

Okay, but maybe see even or someone else want to help with this.

I

Yeah, if, if someone is, is, is really eager to get this done, I'd like to work with them to maybe speed it up.

A

I

Otherwise, I will keep ownership of it.

A

Okay, uh is anyone on the call interested in working with the band on this feature? Basically, it's uh it's already our feature, but we need to implement a uh populator right now, it's in the it's only in the api, but we need the implementation to bring this to data.

I

What what we need is um some changes to. uh I have a design document somewhere about uh changes to the external provisioner side card so that we could do correct error reporting when people refer to a data source. That is not valid, that that's that's one of the important missing pieces.

A

Do we need another cab for this to address those or it's uh all right, indentation? What.

I

uh I believe we planned on amending the existing cap, but a separate cap could also work. I don't I don't. I guess. That's that's what the community.

A

Okay, yeah: we can. We can decide that later yeah, but so there is still some designing design work, basically remaining okay,.

J

J

A

Oh, my this one is crossed out uh I'll figure out later all right. uh Next one is uh cozy. uh Do you have anyone from that team?

A

uh Jeff bryan will count cozy.

C

uh I can speak on their behalf, so they are planning to move to alpha this quarter. They're wrapping up the design uh in the next few weeks, hopefully uh call to action here, is if anyone's interested in helping implement this. They need uh folks to help.

C

So, if you're interested uh in helping code this and helping design it helping shape it in any way, you're interested in object, storage, apis, you're interested in helping develop a potentially new standard. Here, uh please reach out to jeff or sid or myself, and we can worry, shang or any of the other tech leads, and we can help you put you in in touch with the right folks and get you going.

A

Thank you, sad uh okay. So next one is csi ethmo volume, so this one, I think we're putting this on hold because the generic affirmative rolling feature.

A

um So we keep this in beta state and uh I think we need to uh look at this together with the f. uh The generic admin volume feature right.

C

Yeah, I think we keep it in beta and then the line item should be uh aligned with the the other feature.

A

Okay, maybe you should move this one up a little bit.

A

A

Okay, next one is ifs group supporting csi. um We added this one is the alphabet sharing 1.19, so in 1.20 trying to bring it to beta priorities. Two does this look right? uh Is christian still interested in working on this.

I

Yes, I am, I think the main thing we need is an end to end test, which I should be able to create. Okay,.

A

Thank you, so, okay, next we have a few items on csm aggression, uh okay, so the core okay planning is to move into ga uh from outside. Do we need anyone to work on? Do we need a w to work on this right.

C

Yeah, so we need an owner for this. uh The core csi migration code has been sitting in beta for a while. Ideally, we want to get that moved to ga.

C

Is there anybody on the call who's interested in helping with that.

C

Okay, let's leave it unassigned for now, but I think this is an important item and we need to find an owner for it soon. Yeah.

A

And also this is like all of the remaining ones are dependent on this one.

F

A

Okay, so the next one, okay, we sphere uh deviant, is divianco.

A

Okay, it looks like it's not uh okay, so this is the beta uh yeah, so we will keep it to beta because we do have that uh requirement for these two versions we're trying to resolve it. um If that get resolved, then you know we could have a uh target data for ga, but right now we're still working. So so maybe that's beta for now.

A

uh Next one is azure disk, so this one um was brought to beta in 1.19 as well, and uh so now this one will try to hga in 1.20, uh so everything's nd, it's working on this okay.

A

And there's your file, so this one is this one already beta or not beta yet do you know michelle? What's that I.

C

Think it's still alpha. uh There was they're trying to move it to beta last quarter, but didn't make it.

A

F

Yeah, I think, there's just one or two bugs that they needed to resolve, but it should be feasible to to move it to beta this next release.

B

Does it require that uh fact that it uses fs group to mount a file with the permissions like an fs group is not supplied via csi parameters?.

F

um That's a good question. I would follow up with andy on that.

A

Okay, thank you, okay, so next one g c e uh okay, so this one I think it's a beta, maybe 1.17, and then in 1.20, we'll try to go to ga okay. So we have someone work. Oh, this is two okay. Looking for yeah this one, okay.

F

um For now um yeah this might get confusing, but you can put uh your name that matt matt.

F

Yeah, you can put his name on it: okay,.

A

So how do you k, c-a-r-y.

C

Okay, yes, all right.

A

All right uh next one is aws, it's a migration, so this one also want to go. Ga do we have do we have this other mat here? uh Do you confirm this.

F

I think he's not here, but let's just put his name down and we'll follow up with him. Okay,.

C

And maybe put the full name: matt wong.

A

Oh, that this is a matt wall, not okay. Next one is another.

A

Okay, this one is openstack cinder, so you also try to go ga. Okay, so john, you are going to work on this. Miss jung on the call.

K

Yes, I am on call- and I do not have an update at this time- nursing.

A

So uh also you're not sure so immediately.

K

No, in fact, as I said last time there, um the openstack cinder driver is being used. um I I don't think, there's any further action. We really need to take on this one.

A

uh But I think we need to have some code changes to bring this one to ga, so we need to have a like a dev owner to work on this.

A

Do you have someone- or I.

K

Don't have any resources.

A

K

A

Just saying you do, I will see.

K

I will see if I can find someone: okay.

F

I will try reaching out to the openstack community, because I think there were some. There were some engineers working on the openstack, csi migration feature and, and they moved it to beta. So I would try to sync up with them and maybe see if they still have the cycles to move it to ga.

K

Right, do you know who I could contact there.

F

um I think we have to. We have to look up who um worked on the feature, uh moving it to beta it's in the enhancements issue.

K

Okay, I'll have a look.

A

Okay, thank you. uh Okay. Next one is system, aggression and us f rbd, so this one will try to bring to alpha humboldt. So humble is working on this. uh I think combo is probably not on a call. So we just keep his name here and then is he. He has a sign to work on this right.

C

uh Presumably, yes, let's uh put a question mark until we can get confirmation from him.

A

Okay, so next few items uh see seek scalability.

C

uh Before we move on uh for csi migration, I created another tab at the bottom. There, okay.

A

C

And I think one thing I wanted to clarify was currently: we have two feature: flags, csi migration and csi migration complete so far, the csi migration flags have been mostly moved to beta, except for azure file, I'm actually missing cinder and staff over here. I need to add those, but the question is about the csi migration complete flag and what the plan is when those are going to be moved.

A

Should they be in sync, with the system aggression? One though.

C

F

Yeah, that's my question. So the purpose of the csi migration complete flag is to is to say um my kubernetes nodes are at a version where um csi migration is on and cannot be turned off.

F

So I think, to move the flag to ga has to be done releases after the csi migration flag is ga whether or not the flags move from alpha to beta. I I'm not sure that has to be so um strict, like probably we should have moved all these flags to beta.

A

Yeah it looks like ani is the beta.

F

But basically this this complete flag controls um the compilation of the entry plug-in into um the actual kubernetes code. So it actually um like we'll take it take out the entry plug-in.

A

Oh so this would be so this will go together with the removing the code. Then code, removal.

F

Yes, okay, I think, and it it also removes um fallback logic right now. There's some fallback logic in attach detach controller to see if um the nodes are on a version that doesn't support migration or migration is not enabled um this. This feature flag controls that fallback logic and if we turn this on, then that fallback logic is removed. So it assumes that all the nodes have migration enabled okay.

A

All right, then, probably should just shoot when the chinese.

C

Yeah, so we might want to add these to uh to the spreadsheet as well or.

A

Okay, uh okay, just add those notes in for each one of those, then okay, yeah.

F

I think we could just flip them all.

C

A

Okay, so maybe we can just keep the separate ones.

A

A

All right, so our next one is the immutable secrets and config maps. uh Okay, so the plan to go ga uh does this remain the same. So we have uh uh I'm not sure how to pronounce this. uh We have this.

D

A

Yeah, what tech we have tag here, so he will to be the owner of this feature and he wanted to.

C

Yeah, let's leave it assigned to him and uh we'll get verification if he's still gonna work on it. This quarter.

A

Okay, so we'll try to bring that to ga, um then the next one is uh see apps just hpv security pacifist will not be auto removed. So okay, so this one uh there is a. I think there is a cap right that has been.

E

Hi uh this is kkk here, uh so I've updated the uh um like the kept section here, uh the cell, with the comment, uh because I have lost edit uh permission. So if you could uh update that uh with the new caps, uh you know like that. One! That's.

A

Okay, but this one does not somehow does not show us why it's not showing oh it's, because okay.

E

Yep I did that.

C

Okay, I just gave you permission, I think about 30 minutes ago, so you.

D

Might want to retry.

E

Cool I'll give it a shot so latest update. uh I I don't have a meaningful update since the last time, but the latest update that is there is that uh we have some sort of consensus building in the cap um and uh you know like. There are a few comments which I need to add to the kept back and we should get going so I'm still under active work.

E

A

All right, thank you! So, oh just uh so, this is going to you're trying to bring to alpha and then priority three okay. uh Next one.

F

Yeah for the next one right: okay, this is a design.

A

But this one is designs: they still we're talking design for this recorder, the next one or.

E

Yes, I think design would be good, because there is, uh there is uh like dependency between this and uh the resize feature itself.

A

E

And the latest status is that I had a discussion with him and he has given a bunch of inputs which I still need to add. I haven't done it yet, but still actively in my list.

A

Okay, thank you.

A

uh Oh next one is the so execution hook uh yeah. So uh we we had a meeting and then there was some. uh We got some review comments from signaled and then, um but I think right now.

A

uh What we're going to do with this feature is we'll try to have a uh alpha version of the api changes, but for the controller side changes we will try to implement that outside of cubelet to begin with, um and then eventually we want to move that inside the cubely, but that's a longer term, so uh sushant and I will be working on a cap, um so I mean so far. We do have uh some something like google doc, but we want to have a formal cap for this uh yeah.

A

So, let's take it to targeted offer. Let's see.

A

And the next one is a kubernetes eels month suited to a new ripple. Do we have a okay who have a sweeney getting signed on? This is a renee online. Is renee still want to work on this.

J

Yeah yeah, okay, actually it's the as soon as the 120 is open. I think it is I'll try to update the code.

G

I should be ready for review.

A

All right great, thank you. So that's all we have.

C

So one more thing I wanted to call out, I think a month and I talked about volume resizing and the remaining work there. uh I think what we wanted to do was uh call for action and see if we could get more people to help with that uh is anybody on the call interest.

D

In helping with that uh functionality, I can.

E

uh Help sad because I it's directly anyway, in line with the stateful set work as well. Awesome.

C

Exactly great okay, yeah, okay,.

B

Awesome, thank you kk. I have yes, we have some bug fixes planned for uh 120 like uh and then we have obviously the recovery from this failure. Cap and uh we'll I'll try to split the work that could be done, parallelly and write some some stories in the project folder, and then we can go from there cool. We have. We have a project code for each feature in github and yeah. You can pick it up. We can pick up from there.

D

Sure, thank you.

A

All right, great.

E

So I have an update on the file permission handling I just ping uh jing and deep offline, so zing is going to post the issue. So basically, we are uh looking for some input from uh windows expert with more uh file permission, related expertise.

E

So zing is going to post on uh sig windows, uh the specifics of the questions and I'll try I'll help uh follow up on um like getting uh getting a person to get involved here.

A

Thank you for that update, okay, okay, anything else on this spreadsheet.

A

A

So we are done with the 1.20 planning, uh so I don't. We don't have any prs listed here or any design reviews. Are there anything else? Anyone want to discuss.

A

See what's the chat, uh what is this one.

A

Okay, yeah so uh yeah, so, okay, we want to take a look at this yep.

D

Thank you all right.

A

Anything else, if not, you get 15 minutes back thanks. Everyone, bye-bye thank.

C

C