Kubernetes Storage SIG, 11 Feb 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes SIG Storage Meeting 2021-02-11

Description

Kubernetes Storage Special-Interest-Group (SIG) Meeting - 11 February 2021

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

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

Moderator: Saad Ali (Google)

A

All right today is february 11 2021. This is the meeting of the kubernetes storage special interest group. As a reminder, this meeting is public recorded and posted on youtube.

A

uh Let's jump into the agenda so today we're going to go over the 121 planning spreadsheet uh items that this sig is working on and get status updates. uh In addition to that, if there's anything that you would like to discuss, feel free to go ahead and add it to the agenda doc below.

A

If you are a member of kubernetes sig, google group, you should have access to be able to add to this doc so before we jump into the planning spreadsheet, uh I wanted to remind folks of where we are in the cycle, uh so we just passed the enhancement freeze this week, which was on tuesday this week, uh and what this means is that any features that the sig is working on must be declared officially by this date and have their design docs, reviewed and merged, including production review and api review, uh and so today, hopefully, you can get an update on which items uh which tasks that we committed to were able to make that deadline.

A

The next upcoming deadline is march 9 uh in just shy of a month, which is code freeze for the features that we are working on so switching over to the spreadsheet. Let's get status updates first up is from hamanth on delegate fs group to csi driver instead of.

B

B

All right, I want this not fit here so.

C

B

This one still waits for the uh feature merged in the csi spec, but as far as I know, the cab has been emerged.

D

What do you mean, what deadline are we facing on the csi spec side.

B

Well, I don't, I don't think there is any deadline just before the kubernetes freeze.

A

Got it, I guess, is waiting.

E

A

Release or getting merged in the next csi release the.

D

The csi spec pr is out and available for review and I've reviewed it so like. I don't see any reason why, if the kep is merged, we couldn't also merge the csi spec change, release the new csi spec and do the kubernetes coding.

B

It's a different community. Just yes, I spec.

D

Yeah yeah, I don't know I'm just I'm just saying I don't. I don't think it's it's dead. Maybe it won't happen this release, but I don't see why it couldn't.

A

I'll take a look uh at the csi side of things and see if we can get it.

A

Moving next item is csi online offline resizing. um This was basically fixing issues of uh any update on this one, john.

B

I think amanda has some help from other guys in the community and they are nailing down what needs to be fixed.

B

F

On expansion issue and uh I have uh sent a month with a uh whether you draft pr of the fix and I'm hoping to get an update on that soon.

A

Nice, uh do you mind adding your name to uh devlead here you can put a comment next to month. I actually will move him on to reviewer.

F

I don't think I have access to write anything, but if you could write down my name, um it's young s-u-n-g-j-u-n sure.

F

A

A

Next item is recovering from resize failure.

D

There was also.

B

A mute, uh no update, I think.

A

Okay, no worries, uh then we have sc linux recursive permission handling.

B

No update there, okay.

A

uh Then we got csi entry read only handling uh last status here is chang is working on part of this, uh and I think that is still the case and he's going to look into what other outstanding work there.

A

A

Okay, next up is issues related to assuming volumes are mount points. The last status update here was we needed an owner. There was a several prs work in progress. Jing was reviewing any new updates on.

F

A

Next item is storage capacity; tracking for pod scheduling,.

A

Patrick looks like patrick is not with us today, so anyone else have an update on this one.

D

There's also a csi spec change for this one um that I I think I approved okay but uh yeah. It depends on getting that that change into the csi spec.

A

Okay sounds like we need to get a couple of csi changes in and get that new version cut soon as possible.

D

Yeah I spent like three hours yesterday afternoon, reviewing csi spec prs. Nice need need more people doing that.

A

Yeah, we need to look into how to scale that. Okay. Next item is pvc inline, ephemeral volumes with csi driver.

A

G

Cap, the cap merged, um so I think it's just implementation now.

A

Thank you. Michelle next item is csi ephemeral volumes uh actually.

H

The one above the studio capacity, one cap is also merged. Sweet.

A

Okay: next item is csi ephemeral volumes.

I

Yes, this continues to be no um no update. um Anyone who wishes to help out would be welcome. Current plans are to work in the second half okay,.

A

Let's, uh let's go ahead and cross this one out for tracking for this cycle, and then we can revisit it for the next cycle. If anybody wants to pick it up, if not, we can. uh We can come back to it in h2 that.

I

Sounds good thanks.

A

There's a strikethrough button here somewhere there. It is okay spreading over failure domains. um I don't think we've made any progress on this right. Shane.

H

Yeah, no, this one, it's uh depends on the next one uh yeah, so the next one I have done a few updates.

J

H

uh Yeah, so I should schedule review meeting.

H

A

Cool next item is uh csi out of three move: iscsi driver fit and finish: michelle will follow up with volunteers. Karen may be willing to help christian or karen no update last cycle. Any updates on this one.

G

Oh sorry, I haven't had a chance to um to look into this, but okay, no.

A

Worries and uh nfs provisioner, nfs client.

A

A

Okay, we'll go ahead and skip over those. Two next item is volume snapshot, namespace transfer.

E

The nsu and cap were filed for this okay outlines the currently proposed design there haven't been, there hasn't been much activity or comments on it yet, but it's proposed for implementation at 122., so, okay on track.

A

Sounds good and if it would help and things are moving too slowly feel free to kind of schedule. A meeting to review understand all right. Next item is csi volume. Health uh I understand this is the cap was merged.

H

Yeah the club is merged, but we're actually going back to alpha because uh we made one design change, we're moving the extern, the volume monitoring from external agent to cubelet. So we actually added the feature gate. So now it's back, but the controller is still the same, but the note side will be changed, so we will keep with uh we're just staying at alpha, um yeah and uh yeah. Then she is uh going to make the code changes.

A

Sounds good. Thank you and next item is volume. Populator data source.

D

um Yeah the uh the cap for this is merged and we're on track for implementing it on 121.. I, though, the one thing is um uh tim hawkin had suggested that he wanted to continue discussing some of the some of the api, some of the corner cases in the api design- and I don't know uh if we can get him to show up at our tuesday meeting or if we need to schedule a one-off meeting for that.

D

Did you ever hear back when you.

A

Suggested you come to the tuesday meeting. I have not heard back on that. If you poke that email thread again uh and ask him, we should be able to get a response. Yeah.

D

Yeah I'll encourage him to come to the tuesday meeting and if he.

A

D

Then we'll try something else: yeah.

A

I think just scheduling his calendar is difficult, but yeah he'd be we can. We can find some time with him. uh Next up is cozy uh jeff or john.

C

This is trini. uh Actually, api review is in progress for cozy. uh We had a one-on-one with tim hawkin.

C

He has expressed some questions around the mutability of the objects, so uh we could not uh hit the deadline for changing the cap to implementable, so we're going to continue with provisional.

C

We will have more discussion on the mutability issue, uh so in the in the meeting after this meeting, and eventually we need to get back to the team and we are trying to also bring him up to speed so planning to have another meeting with him.

A

Perfect, okay, so I'll go ahead and mark this as design for this quarter and hopefully we can get the cap approved and then next cycle will be unblocked.

C

Yeah, that makes sense uh even the development progress has been stalled a little bit because of this uh design issue with the api objects, so.

A

It makes sense you guys are going through the hardest part of the design review right now, so understandable, yep. Okay, next item is change. Block tracking uh anyone want to talk to this.

H

Yeah, so uh we actually had a design review yesterday. Yesterday's the deal protection, one group, uh so we got a lot of good feedback uh yeah, so I think we will need to keep working on it. We actually still need to get some feedback from ebs side um the api, because we couldn't come up with a common api that also support vps, it's a there. It is a little different, so I don't know if anyone else call uh is familiar with the eps api.

H

uh If you are please, uh let me know.

K

Hey I back from aws here uh feel free to pick me. I can help you all right. Let's get the right person, we.

H

K

Is that it's a y b e r k.

H

O a y b: u r, k okay.

K

H

All right, thank you sure. What is your uh slag? What is your.

K

uh It is the same. Oh.

H

Okay, all right.

K

That's my name.

H

A

Cool all right next item is new read, write uh once access mode or read, write only uh last update here was doing research on this we'll open a cap later. um Yes,.

L

Are you on the line.

A

L

Am um so I have an enhancement issue wild, um it's number, two, four, eight five, um uh there's no pull request opened yet for the actual cap, but just the enhancement issue um and then I'm just working on a draft, a draft of it right now.

A

Perfect thanks chris.

A

Oops and put that in the wrong box.

A

uh Next item is update: topology labels from beta to ga jaway.

M

Yeah, um so this one, um the pd says the gcpd part has been done by me and the other, the other um plugins. I think lila is working.

J

M

I haven't heard back from her.

J

Yeah I've been working on the changes for azure disk and azure file, so hopefully I'll be submitting.

M

J

Pr for that soon,.

M

N

Good awesome, thank you both.

N

uh This is deep. I had a quick question on topology. This is the volume topology right.

M

Yes, this is the the pv uh the topology that on pv, so it used to be failure. Domain beta, something but right now we're updating that to the ga version, which is topology, kubernetes io, something.

N

I see, but the topology feature itself is already ga right. Yes, okay,.

G

N

A

All right next uh we're going to move into the csi migration section uh so with the core um joey. You want to give an update here, yeah for.

M

The core, um I think, the the only remaining obstacle uh outstanding problem is the matrix. So um there are three parts around the matrix that I'm changing right now. The first part is to uh add the fill to the csi sidecar.

M

Operation, duration, matrix so basically add a migrate field. There and second part, is add a migrated file to the storage duration operation seconds, matrix um yeah, that's the second part. The third part is to add a new matrix to cubelet, which currently I named it csi cubelet operations seconds. So basically, this one is to capture the csi operation from the node side, so the existing csiro sidecar operation seconds. It only captures the controller uh call.

M

A controller says I call from the set cars, but uh the the node side operation are all missing and this one is to cover that. So that's that's about the matrix um and other than this.

M

um I also update the the cap so where I think the editor file should be unblocked um yeah, I think that's mostly about it for the core. Okay, thank.

A

You next item is a csi migration for each of the different plugins vsphere is up first divian.

A

Or anyone else able to give an update on vsphere behalf.

H

uh I think we don't have anything new other than we have already discussed, and so we're going to have a meeting with the sig architecture later, just to figure out the deprecation part.

A

That's right uh so yeah if anybody else on this call is interested. uh The sig architecture meeting is today at 11 a.m. Pacific time so feel free to jump on that. If you're interested in discussing the vsphere deprecation topic.

A

Next item is azure disk, uh andy or michelle.

A

Or jawway azure desk.

G

I think azure disk is remaining as it is, azure file is being targeted to beta, and I think andy has appeared out already.

A

Okay I'll go ahead and scratch azure disk for this cycle since we're not working on it and then on the gce side. uh Last update was we'll turn on by default in 121, but remain in beta.

I

Yep, that's yeah, that's that is still um on track. We look there's the two biggest things. That's aside from the metrics that we're working with joey with the core stuff is.

I

uh Regional uh pds, as well as uh windows, support, um there's a minor bug around naming for the regional duties which we've identified and the window support. We are manually testing and it seems to work, but we're still working interesting issues.

B

uh I have a question here: does it mean that the kubernetes will have the migration enabled by default in 121, because the last time the information was that gke will have it one by default? Only and not kubernetes.

I

um I think we were thinking of turning it on in 121, but there was uh yeah we're still that's still the plan for so again. This is just for these migration um yeah. If there's concerns about that, we're definitely willing to hear them. But I don't at this point's too recent enough to turn it on.

B

No, no I'm just fine, I'm fine! I just want to know what's in kubernetes and what's in gke, open source versus gke yeah, open source.

B

So it's owned by default in open source 121.

I

uh That will be the plan yeah.

B

A

A

Okay: next item is aws.

A

K

We are now targeting on by default in 122.. uh Let's stop it. I have, but we have you're getting help from evs, so we are going to make more faster progress on this.

A

Awesome, thank you for the update.

A

uh Next up is openstack cinder.

B

All right, so I looked for a sickle provider and the work workgroup for openstack and they haven't met for a year. So.

B

I ask on the slack they want to be enabled by the effort in the 121, but there is not clear ownership of the task that needs to be done, like the testing and ci, and these kind of things.

A

Interesting this sounds like a topic for sig architecture sounds like uh cinder has been abandoned. Oh no, like people are working on it.

B

But I don't think they meet interesting.

A

That's not good um ever poke more okay, so let's say.

A

Cool thank you for following up on that. Yawn next is ffs and seth rbd. Anyone able to get an update on this. I think humble's been out. uh He had some personal family uh stuff that he was dealing with and uh hopefully, when he gets back, we'll get an update on this one.

A

Next item is ungraceful node shutdown.

H

Yeah so uh I updated the cup. um I think I actually just see some comments there. uh I will continue to work with uh ben and jasin on that cool.

A

Okay, next item is enable username space and cubelet, so uids get shifted.

A

Last update here was need to follow up on cap.

A

Anyone have an update on this one.

A

Is mauricio on the line nope.

A

Okay, next item is immutable secrets and config maps uh last uh status update here where caps npr's are approved, uh so I need to double check whether they were merged or not, but should be pretty close to.

G

Yeah they emerged, they.

A

Merged okay, any outstanding work left.

G

I don't think so. uh Maybe documentation.

A

Okay, oh well, we've already marked it as done nice. uh Next issue is address issues with pvc created by stateful set not being auto removed.

I

Yes, so sorry we got the uh I'm a cap uh merged for 121., um the the actual pr changed. I put in the uh comment of the uh kept pr number, the actual pr that um got it merged um and uh yeah. So it's merged for 121 and we will hopefully make the implementation uh deadline.

A

Awesome, thank you. Matt. It's going to be a nice usability, improvement.

I

Oh yeah, so um I guess sort of one procedural question here, so it turned out. We got the kept merch under the sig apps um ownership. um Okay, I.

A

I

Like does that mean we want to like transfer tracking over there, or do we not really care that.

A

Don't think it matters yeah as long as it's being tracked by the release team, which it is, uh which means the cap has been merged and it is being it's in the new release, spreadsheet and you're all good, okay, okay, cool cool next is volume expansion for stateful sets.

A

I don't think we have an update on this one.

A

Next is execution hook.

H

Yeah, so shenzhen is still uh updating the caps. He is going to schedule a api meeting with tin, so I will paint him on that.

A

Yeah, I think he put there's something scheduled for this afternoon.

H

A

Container notifier, I think it's internal for now, okay yeah, it looks like he's following up on it. um Next item is split into new repo. The uh kds utils mount yeah.

C

Yeah, this is really, I don't have any update and I'm I'm sure that we will not have any update until the code. Freeze c advisor has moved to use moby library for multitel, so once they merge, they do that, usually after the code code freeze, so I have a pr uh slash hold on it, so once they merge, I will merge my pr. So it's not until then I don't have any work. I think to do.

A

Okay, so should we continue to track this for the cycle or.

C

Yeah, it will be moist as soon as the code freeze, but okay.

A

It's tricky that depends on whenever that happens. Okay sounds good. Thank you. Serenity.

A

uh Next item, six scheduling, prioritization on volume, capacity.

A

uh Michelle or yan.

G

The cap has merged for this.

A

One: okay and then finally, user id ownership in config maps and secrets, shawway.

M

um I haven't got a chance to look at this I'll look at this next week.

A

Sounds good all right! Thank you. Everyone for the updates. Now, switching back to the agenda looks like we don't have any pr's or designs that need review miscellaneous uh generic tool for csi sandeep. uh Let me hand it over to you. Do you need to share anything.

H

I'm not sure if sandeep is on a call. I actually copied this from last meeting ah looks like it's actually not here so yeah, okay,.

A

uh Maybe we can save it for next time, yeah.

E

A

Can present it okay, so.

A

Okay, anything else uh folks want to talk about today.

A

Any follow-ups on items from previous.

A

A

Okay, then we'll end early and we'll get 25 minutes back in your day. Thank you. Everyone, okay, thanks.

M

Sean thank you.

A