Kubernetes Storage SIG, 9 Feb 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes SIG Storage Meeting 2023-02-09

Description

Kubernetes Storage Special-Interest-Group (SIG) Meeting - 09 February 2023

Meeting Notes/Agenda: https://docs.google.com/document/d/1-8KEG8AjAgKznS9NFm3qWqkGyCHmvU6HVl0sk5hwoAE/edit#heading=h.2g804193gwqo

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

Moderator: Saad Ali (Google)

A

uh Today is February 9 2023. This is the meeting of the kubernetes storage special interest group. As a reminder, this meeting is public recorded and posted on YouTube, uh so we're going to go over the agenda today, starting with uh 127 planning um and then we'll move on to any PRS, discuss design, reviews and then miscellaneous items.

A

If you have anything that you want us to discuss, please feel free to add to the agenda and you can find the link in your calendar invite uh so that we're going to switch over to the planning spreadsheet uh reminder that uh today is the enhancement freeze uh and the next upcoming Milestone is going to be uh the 14th of March, which will be code freeze for this uh 127 release, and so with that I'll go ahead and switch over to our planning sheet and we can get started getting status updates on the items that folks are working on, um I'd be curious to see which ones we were able to make the kept freeze for uh the enhancement freeze and which ones uh we weren't.

A

So with that, let's get started first up, uh I think I see Jing on the call we have recovering from resize failures, end-to-end tests uh a month or Jing, either a few on the call.

B

Oh yes, so I think this is a cab ride and the command is, um and the young is reviewing.

C

If I may add something, uh we decided to update the API to accommodate the changes for quality of service and that's why it's going to stay Alpha in this release. It will not graduate I. Think hemanth is updating the cat, but since it's going to stay Alpha we don't need any prr got it.

D

I think the cap is already merged.

C

A

Cool, thank you folks. uh So it was Alpha. It's gonna stay Alpha, I'm, gonna, change that and.

E

A

The additional work here is uh incorporating uh qos.

C

Oh not really just open the API, so POS can be edit easily and we can graduate uh the recovery from precise payrolls early and we don't need to wait for viewers to VGA got.

A

It okay cool. Thank you, John!

A

All right. Let's move to the next item. uh Issues related to assuming amount volumes are Mount points um anything new on this one.

B

So we do I think, discuss uh this type of issues in the CSI triage meeting and uh we have some uh thoughts and ideas how to uh improve this and I'm trying to find in our site. Anyone can volunteer to work on this.

A

Cool, thank you Jane, and if anybody on the call is interested in volunteering or looking for a place to jump in on kind of bug, level, issues to help with this might be a good opportunity. So please reach out to Jing or one of the leads, and we can help you get started.

A

Thank you. Jing next is uh volume group API and seeing some good progress here showing you want to update.

D

Yeah, so the cap is finally merged needed um uh and the the CSS back. uh So uh thanks, uh Assad and uh Ben, you approved it uh this morning, I found some new comments from James, so I'm, just looking at that, have not got a chance to uh address his comments yet I think mainly. He still has some concerns on the deletion. The deletion API. Maybe the I know we add a lot of comments. um uh The the group ID. Sometimes we need that.

D

Sometimes we don't so I think he has some question and then he has some questions on the the get API as well. uh So I'll take a closer look and address that later today, but he did say that it's getting closer to the finish line. So so, hopefully we can wrap this up soon. Cool.

A

Thank you Shane. This is, uh this is a huge.

D

Thank you same thanks. Everyone for helping the reviews, yeah.

A

For sure all right next item is provisioning volumes from Cross namespace snapshot. Pvc. Any updates on this one.

D

I don't see much I've seen, there's a they opened an issue. The author of The open some issue on the voting populated repo, but I, don't remember seeing any PRS opened yet.

A

Okay, we'll keep an eye on this. Thank you. Shane uh next up is CSI volume, Health, additional metrics and or events. uh This is moving to Beta.

D

I think we missed this. The the E2 test is uh still not ready. uh Running is working it, but it's just. There was a walking progress PR, but I don't think he has finished that yet.

A

Okay, so I'll uh change this back to Alpha for now and then okay and Target data next time.

D

A

uh Change block tracking uh targeting Alpha this cycle. Did we get that kept in.

D

No I don't know if Yvonne or anyone here uh so we're still discussing it. There are still some issues um you know, which is the right way to go. I think we are now a design article or go through this. uh The aggregated, API server away, um but I think still being discussed in the data protection group meeting. I, don't know if a band is on a call with anyone or because yesterday I couldn't join the call yesterday, but no yesterday uh they were still discussing this.

A

Got it cool? Thank you, Shane yeah! This is a complicated one, so it makes sense that there's still outstanding questions here, yeah uh we'll keep it in design for this cycle. Okay and move to the next one, new rwo access mode, uh moving Alpha to Beta any cap on that one.

C

I think that merged nice yeah.

B

A

Okay, so that looks like it's on track: uh next is runtime assisted mounting. uh This is was trying to go to Alpha this cycle. I think this is put on hold uh is deeper anybody else on the line who knows about this.

C

I just know: it's moved to 128.

B

D

So I think the uh I think the status looks like it's still same as last time then reviewed the CSI spec PR and he said he's going to update it. Based on the comments but I have not seen an update on the seats. I think.

A

Yep that makes sense so I think we'll keep this in design for this cycle.

A

Cool, thank you Jan. Thank you. Shang next is CSI proxy for Windows transition to privileged containers. This is out of tree work. uh Trying to go to Alpha uh looks like Mauricio is assigned to this uh deep reviewed it. Anybody know if uh kep got merged.

A

uh Jane, do you happen to know about the CSI proxy work.

B

um I I don't think it's get merged. Yet we.

A

Got it so the cap cap is still open.

C

Oh, and is there any cap, can anybody please add the link.

D

So this one is not being tracked, because this is like we're.

B

D

Following the deadline, no, you know the foreign, so that's why it's.

B

Not yeah, let me find it and I did there is.

A

The cap even needed, then, if it's I.

D

Think we still decided to do a cap, never believe, and there was a cap that I have never reviewed it so got it. I believe that this decision is which you need to write the you know the design.

B

D

Think in the in a cup, that's why we need a cupboard. We don't need to go through the formal uh deadline. Thing.

A

So we'll still Target uh 127, since this is out of Creek- is that an accurate summary.

D

And yeah we're not really fully any particular release. I think, since this auditory right right, I I, don't know, yeah I think we.

D

A

Okay, uh thank you. Shang next is node expansion secret. uh This was Alpha to Beta um end-to-end tests. Work in progress plan is to get ready by Monday anything new on this one.

D

So this is something we want to discuss. uh This one is getting very close. Now there is a e3 test, um so the only thing is it's a alpha test, so we basically need to add this one to the other job that PR just got um so uh so after this meeting the later on this afternoon, I will I will see a business need to trigger that job to see. If the you know, the job I mean the test shows up in the test group.

D

That's that's one thing we need before we merge it before we merge a cap, but but since the deadline is today right, so you've noticed anything uh goes around uh both um humble and Luis. Who is working on this one? They are in a different time zone, they're they're done for the day, so we're discussing this with uh yeah and also Michelle before even before she left. We were talking about whether we want to just get this merged just a brand, an exception from our side. Michelle actually mentioned that she has seen some caps.

D

uh There are other six. They are not really as strict. They are not requiring degree tests they're. Just looking at the unit test before they merge a beta cap, so um yeah, that's the thing I want to discuss because I don't want to uh be too vague that we don't know. You know what is the process. They are right, but this one is definitely getting very close. So if everybody is fine, uh maybe we just say hey. This is a special case. We can. We are making an exception together.

D

It's not merged, so so that we don't have to scramble to. You know, get and try to get an exception in a couple days.

B

D

A

That makes sense yeah yeah if.

D

Everyone you know, young, we talked about it and Michelle seems to be spying as well.

A

Yeah, if they allow it I, think yeah, let's go for it and.

C

uh I am fine with emerging recap, because the end-to-end test is close to merge mm-hmm.

D

C

And people are working on it like they are not going to leave.

F

C

D

F

C

D

Sure, yeah I'm, fine, okay, let's just go for it. Yeah thanks.

A

Cool. Thank you. Both uh next is SC Linux relabeling using Mount option. Csi driver API change.

C

It was merged, including prr, nice cool.

A

Thank you, eon looks like that's on track. uh Next is CSI migration stuff, so uh first up is removing entry GCE.

A

um We were looking for volunteers for this one did any update on that. Did we.

G

No haven't haven't, heard anything uh from that and also I guess. This is waiting until right. This will be a 127 at the soonest, maybe an extra version, because it just went GA and 125.

A

Got it uh so meaning uh hold off till 128 on this.

G

One yeah, okay, yeah.

A

So I'll put uh in 128 here and we'll stop getting status updates on this. In the meantime, if anyone's interested in doing this work, uh you know it's always nice to do work where you're removing a bunch of codes, so this might be a fun project. So if anybody on the call is interested, please reach out to Matt or myself or any of the leads we can get you in touch with the right folks.

F

This is Manu from Amazon I just wanted to understand a little bit more about what this work entails. uh We might be looking to help contribute in the future, and uh if this is not something that's especially time sensitive, we might be able to take this up in the future.

A

Yeah, that would be awesome um so, as I understand it, the work here is uh finishing up the CSI transition, uh so there was a bunch of old entry volume plug-ins uh for some Cloud providers and a handful of storage vendors and uh what we did as a Sig is try to transition most of those to CSI during the CSI migration work, as that work finishes up, but.

G

A

Follow-Up is to remove the entry code at some point and so uh effectively. This means you know going in and deleting that code and making sure that you test to make sure that the CSI migration still works, and things like that. uh So that would be the high level work, but uh folks, like Matt, can walk you through the actual details of what needs to be done. For example, in this case, it's the GCE, plugin and you'll see uh items for for all these different plugins, where we actually need to go and do this so.

F

Got it uh yeah, maybe I'll reach out to you offline, uh to get some more context around these things. I think we may be able to help in some of these activities so uh we'll we can review this. One awesome.

G

Cool cool- that's that's great. The um I think the best way to get in touch is over uh Slack. So, okay,.

C

We already did it for cinder for openstack cinder, so there is a pull request that can be taken as an example and nobody complained so far. Nice, okay,.

F

Great, that's that's helpful to know thanks again.

A

Cool thanks uh thanks for offering Manu and uh reach out to Matt on slack, and then uh we can get connected.

F

Yeah we'll do thank.

A

You thanks, uh okay, so next one I'm gonna skip over VMware since that's targeting 128 uh and then on the AWS side. We have AWS, EBS and Azure disk also need to be removed. uh Last status here was also looking for volunteers, at least for the AWS EBS side. Manu. Would you be interested in this one.

F

Yeah so I think Eddie uh from our team is signed up to to do this work and he's on the call. So he can provide an update.

A

D

Yeah, so no big.

F

Updates for this week, I've.

A

Blocked out some time to work on this next.

F

C

B

C

Remember correctly that the GCE and AWS EBS graduated CSM migration at the same in the same release. So should we remove them in the same release.

A

I think GCE was supposed to be released or removed in this release, but uh we were waiting on volunteers, so we're pushing okay. Okay, sorry.

F

I think yeah AWS I think we did our migration in 123. If I'm not mistaken, I'm I'll have to go double check, but I think uh we became default in 123., so yeah.

C

And G8 was 125, I believe so yeah, it's the same like GC, but.

E

C

Remove them at different time no issues with that.

G

A

And next one is the Azure disk uh and anyone have an update from Andy.

A

Okay presume this is still in progress uh and then Azure file. We are pushing to 128.

A

and uh ceph RBD beta off by default. uh uh Any updates on this one.

D

So homo said they will update the test this Friday or by early next week. So we'll see you test uh can be done. If a test can pass, then we can see if we can apply for exception. Maybe for this one.

A

Got it cool, thank you, Shane and then uh CFS same thing or no.

D

This one um he didn't really uh commute on this one, so I think this one should be removed.

A

Got it okay, so I will uh just cross it out for now.

A

And then Port Works uh anyone.

D

Yeah they did indicate they didn't get back to me. I pinned the uh Oksana, but she didn't get back to say whether they want to do it or not. So.

A

Okay and says no, everybody on the call is uh nose, Port Works contacts- if you could reach out to them and ask them about this. That would be helpful.

D

Oh I I'm talking to uh the Oxana space today after that, uh that's it so it's so basically they they're not ready to do it. Okay,.

A

D

Again, yeah I can I can ping her again, but but but I already asked her a couple times so I just they didn't really commit on this one, and it's already too late for 1.27 right. We already passed the cap, merch deadline.

A

So, let's just cross it out for the cycle and then we can check again next cycle and.

C

Even the issue uh enhancement issue was closed.

D

Oh sometimes, maybe it's because uh if it's linked somehow it's a fixed systems and then the party I.

C

Don't know it expired like because it didn't have.

D

Oh I see I see that if that's the case then yeah, then we can just uh you can just revive it. Okay! Well, this is very okay. Let's see why this one is closed.

D

A

Okay, we can follow up on that offline. uh Next is always honor, reclaim policy. uh This is made moving to Beta. This cycle um looks like last. Status was may not have time for this in 127.. It.

D

Was yeah that was it uh we didn't get time to add the E2 test, so this one is a mode out to the next piece.

A

Let's go across this one out, foreign.

A

Volume mode conversion between source and Target, PVC.

D

Yeah, so the cap is merged, we do test got merged, so a cap is also submerged.

A

Nice good progress.

A

Right, thank you. Shane. uh Next up, better default storage class. uh This was trying to GA this cycle.

D

I think it's it's next, where we'll have to wait for I. Think this one. Oh.

A

This is 128 right, yep, okay, uh then quality of service for volumes uh Alpha for this cycle. How did the cap for that? One go Matt.

G

Oh um sorry, uh this is the stateful Set.

A

The quality of service.

G

Oh no, these this uh did not go to Alpha we're gonna, do a provisional cap um this cycle and do alpha uh the next cycle.

A

Got it okay, we'll do provisional cap for 127 and Target Alpha in 128.? uh Do we want to keep tracking this uh for 127 or just cross it off and bring it back for 128. I.

G

Think cross off and bring it back for 128., okay,.

A

Cool thanks, Matt uh next is efficient, Mount time handling of FS group.

E

Yeah this this is design only I think it's a similar boat, a similar boat to the previous one. uh It will be provisional, I'm still working on the cap. I've made some updates this week and I expect to have that out for review in the next week or so.

A

Got it and Jonathan, do you want to uh keep tracking it or cross it out.

E

um I think it's okay! If we cross it out and track it for 128.

A

Okay sounds good, so just scratch that out cool. Thank you. Next is robust volume manager, reconstruction. uh This is also going beta. This cycle.

C

Yeah I think yeah a good merged. That's on Direct.

A

Cool thanks John uh and let's move this guy up before we go to the crossing ones, uh PV last phase transition time Alpha for this cycle again I got merged, got merged, awesome.

A

Okay! Now we can switch over to the Cross Sig uh items. The first one is non-graceful node shutdown targeting GA this cycle. That's.

D

A

Okay, perfect! So then, let's skip over that and grab these two.

A

uh So this one is uh address issue PVC, created by stateful set, will not be Auto removed. uh Targeting beta this cycle.

G

Yep this is approved for uh beta prr has been approved. The kept templates been updated, all that all that stuff, so um we are good to go and then the uh just as it may be of general interest. Part of the issue has been because of um CSI migration. The cloud provider extraction a lot of the alpha and end tests were not running with a default storage uh class and um because, as it turned out the default, the alpha feature flag.

G

End-To-End tests were running on a GCE um and I am working on getting a kind uh setup which should should help with all that testing in the future to make it a bit more stable.

A

A

Last item we have is volume. Expansion for stateful sets um any update on this one.

A

Okay, we'll mark that one as no update and come back to it next time. uh That is it in terms of updates. Thank you.

A

Folks looks like we're: making good progress for 127., uh switching back to our agenda doc, so miscellaneous item for announcement, um Sig storage is looking for volunteers, so we mentioned some items in uh the planning session, but in addition to that, some areas that need help right now are investigating a better vulnerability scanning method for our projects, um building tools and scripts to make it easier to do sidecar, releases and tooling to improve our issue triage.

A

So if anybody is interested in helping with these items, please reach out to Michelle uh and uh and she can get, you started on uh guiding you on on where to get started here.

A

uh With that, any other items to discuss today.

F

um Yeah uh so I've left some comments on the qos cap. uh If Matt could look at that, and some of them um that'd be good, um do you plan to release like an updated version of the Caps anytime soon.

A

B

G

uh Yes, we uh have been preempted by a couple of things, but we're planning on getting back to discussing um the captain, just as an ascitis like our hope for uh 128 is like not to do a final time scramble right before um the uh freeze, but to actually get it get it approved in the next. You know a couple months, um so, yes, we are going to be hoping to get back to that end of this month um and work on it in March.

F

Cool thank you. um I had a quick question, uh just a matter of process more than anything else. uh If, if there are questions on the cap, uh is this typically the right Forum to discuss those questions, or would there be like more detailed discussions elsewhere.

G

I think this is um a good um Forum like you know, especially if it's a overview question and then you know if it turns out to get into a much more detailed conversation, then this is a good forum for figuring out uh a meeting to make and then we can kind of break off um and discuss things but I think, at least in my experience. This has been a good place to raise issues because that it gets good uh home visibility.

G

um It also works out pretty well to start conversations on Slack.

F

Got it yeah uh I was asking because uh we've been having some internal discussions regarding uh uh how do we expect the cap to work for the AWS, uh EBS CSI driver and that's what's driving the questions that Russia is asking so I just wanted to understand. If this was the right place to bring that up or not so.

G

Yeah absolutely like that's. This is exactly what uh we'd hope um would happen, I think having any feedback you have on. This is yeah. That's exactly.

F

Sounds good. Thank you.

A

uh Manu, do you want to elaborate on that now or do you want to do that in a follow-up meeting.

F

uh I think it would be helpful if uh Matt goes through the questions uh and gets the chance to think about the responses in a little bit more detail, uh mostly I, think the quest the the concerns that we have are that you know there are certain areas where the capital seems to be somewhat ambiguous and doesn't necessarily specify the correct, behavior and and we'd like to make sure that we can get clarity on those those items, because uh I think that will determine how usable uh this this functionality would be for our customers.

F

So so that's that's. Basically what it is.

A

Oh sounds good, I, think uh Matt, you can follow up offline and, if needed, we can use a subsequent meeting to discuss further.

G

Yep, absolutely absolutely absolutely.

A

All right with that, any other uh items for discussion today.

A

All right thanks a lot folks. I'll see you next time.

F

Thank you. Thank you.