Kubernetes Storage SIG, 9 Apr 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes SIG Storage 20200409

Description

Kubernetes Storage Special-Interest-Group (SIG) Workgroup - 09 April 2020

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

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

Moderator: Xing Yang (VMware)

A

All right, everyone today is the four nine nine twenty twenty. This is the sick storage bi-weekly meeting this meeting will be recorded and uploaded to youtube. Today we walk over the 119 plenty.

A

A

So we have this planning sign-in sheet for a 1.19, we'll just go over item by item and find out the owners and see who will be working on it. The first one is it's the first, it's the first one sees a migration. Next steps. Do we still need this item? Mushara see you added a few individual items for which club provider.

B

Yeah I think we can replace this item with the per cloud provider items. Okay, cuz I think the core CSI migration framework is all in so just shred.

A

This one, so we have okay, so we had the piece here: CSI yeah we'll be working on that trying to get it to beta.

A

Actually, on okay, so who will be the? Is it beta or alpha we're trying to go beta? If we can get a CI, then we want to get it to beta. We couldn't guess yeah I, wasn't then of course, then it has to be alpha, but we are trying okay, trying to you, get your beta I, don't know who I should put on as a oh just leave this one for now, but I can help. Give you an update.

A

Who should be the reviewer here.

C

You can prove.

D

Me for now, oh there you go who's.

A

D

This is Jonathan ba Surrey. Mr.

E

Heyman, okay,.

A

E

A

A

The next one is, as you see, some aggression.

B

So I think um Andy from Microsoft has been the main person working on this. Oh sorry, column, I/o,.

B

As a for a reviewer, you can potentially put my name down for now. Okay, I'll probably try to find a replacement reviewer, but I will be the placeholder.

A

Do you eat what about so? Gcp is all set.

B

A

B

Gcp, AWS and OpenStack are all beta we can contemplate if we can contemplate if we want to try to move any of those plugins to GA. Okay, so probably should still have some something here just to yeah.

A

B

Let me I'll add some okay.

A

So I'll just leave that to you, okay and also do we also need something at the end to remove other entry cloud providers. Would that be like one, the vitamins or should.

B

We just check that with each I think I think we can track it with each plug-in and I think we won't. We won't do it the same release that we make it GA like we'll, probably make a ga and then one or two releases later then we'll remove it. Okay,.

A

Si si online offline resizing, so we trying to what is the what will be the target is thatis for when I nineteen I.

E

Think it will remain in beta at least one nineteen, because we.

A

Have to consider.

E

The next item, but we are I'll, be working on fixing the issues that we have. The.

F

E

Ga, there's a project, a sport that we are tracking every all the issues: yeah, okay,.

A

Sure so just leave it to beta, and then himand is still that that lead a peer reviewer, sad reviewer, okay, so we should remove Dave, now, races, she's, not working this anymore.

C

Yeah, let's replace David so.

A

He's been still the right reviewer do we need anyone else here? The.

C

Ben, are you on the line and okay with that? It's.

A

Been I can.

G

E

Also also like Ben he's online, but he has been reviewing the changes and and every PR the iPod. So okay, okay,.

A

Next, one is support.

E

Might want to uncross it because.

H

E

A call we largely agreed I I need to talk with zinc offline or like set another call, and and finalize this one will largely agree to have the cap implemented as proposed, but our changes to get it done. So we.

A

Have will have a cup, can you at least I.

E

Don't see any cup, do you also have a.

A

Enhancement issue: it's also not here.

E

A

And this is steel beta in Ueno, 19, yeah.

E

A

Okay, so it's a hormones that lead it's not as a peer reviewer. Now this day we need to change it. Is that jin-joo, the machine? Is it.

A

Next one is support containerized as a side note plugins in Windows. So is this one? Oh nice! Let me check. Oh I thought this one says it down. No, this is not started at you. One. Yes,.

B

It was alpha and 118.

A

Okay, okay, I think.

B

The target is beta mm. Okay, rank sensor.

A

Okay, okay, so we still okay, so we have a deep deep was to be work on this right. The deep yeah.

B

I think so: okay.

A

Let me show is if your reviewer and change their view, so those are all fine. Okay, a snapshot, it's going to be still be beta. Now 19 we're try to bring to you GI in 1.20, so we'll just to keep fixing bugs so yeah me and Shanshan working on the she'll be reviewer, so I think that's fine!

A

Next one is a recursive now recursive warning ownership.

A

This is this. The beta is this. There is this the right target I! It's alpha.

E

Right now we're trying.

A

E

Two beta in 119.

A

Okay and okay, so come on is stay with that lead. Yan is doing if you review and Jing is revealed, so those are still fine right, yeah, okay, next one secure, Linux, recursive permission handling, so this is a design okay. So for 1.19 we are just trying to get the design I.

G

Have a out and I could implement it as all floppy. Okay,.

A

So you want to try alpha I can.

G

A

Okay, so crap here so yeah will be the don't lead, come on baby reviewer. Do we need a APL review for this one? Yes,.

I

A

I

A

I

A

A

Okay, we'll just leave it for now. You.

B

Can? Put me down okay,.

A

Okay, so this way is crossed out we're not doing that. Then you design flow, wouldn't file commission and Elaine. Now we have a item for five mission: Hannah little windows, so deep, we'll be working on our design in when our 19 is that right, I.

B

Think it needs to be investigated if we need to do this or not. Okay. Oh sorry, KK are you here, yeah.

J

So we've been trying to discuss this in the CSI proxy meetings, but we have not yet gotten the right folks to discuss from, like you know, windows, side of things. So it's like a group effort at this point and you have not really finalized sort of about this forward, so maybe like either me or they will keep updating.

A

Which is KK here as well yeah.

J

You don't what I was trying to say. Is it maybe it's a good idea to consider. This has not started. Okay,.

A

Yeah yeah, it is says, not started so yeah yeah yeah, that's that in here. Oh, but this. Why should say starting right this one? This is not started online offline resizing, that's ongoing. Should we change this? What you started, yeah.

E

A

E

Yeah: okay, oh.

A

And also now, apart the priority: do we just keep all of those priorities so right now we are let's.

C

Take a look at them as we go along.

A

C

A

C

I online all signed resizing keeping it in beta I, think that seems reasonable. We should keep on working on fixing the issues they're.

I

C

From resize failures seems like we need to, and maybe we could, if we broke out there recovering from resize, we could keep that as one and move to second and the first item number 3 p2, maybe the month. What do you think or both p wanna.

E

Sorry number 4 can do SP I think because this is.

A

E

A

Do we want to fix those before or GA? What do you think.

E

Yeah, there's, like largely we agree, I agree to fix it.

A

I

Sorry come up, you cut out all.

E

Right sorry, I was saying that for what item number 4 there's a manual work around that works, so if I know I mean the last call we agreed and Jing had some concerns and we'll schedule. Another call: ok, yeah yeah off chance. We say that ok, this is not something we need to fix, because the manual workaround is enough and quota system will be broken and on all this consideration. So it's probably fine to have item number for sp2. In that sense,.

E

But still I would really love to fix it. Yeah.

A

Okay is that okay, good.

I

C

Yes, I proxy I. Think that's fine to keep chugging along on that snapshots is very important. We need to keep working on it. Non-Recursive volume ownership is a huge issue. A lot of people are having one makes sense, selinux recursive permission handling.

C

Do you do the apt I think makes sense there? It's lower priority than the main feature file permission. Handling for Windows as p2 is fine.

C

A

Yeah, so this one do we have anyone working on this on this call? This is the one that Mike brought up in the last meeting.

A

Is already code, is there there's.

E

A cap in there's a kudos, oh.

A

Okay, okay, yeah I, don't see them. Okay, I will link them after this call. Okay. So this, what won't you bring this bunch of half-hour? Why we seen it was already code right, Martha. It's.

E

Probably going actually, it was already beat us, it's probably going GL. Oh.

A

Just after fixing this one, when you change this to UGA yeah, that's the that's the goal. Okay, then, what's the priority for this one.

B

So I think this is largely driven by sick off it might I guess we can check with them on what their priority for this is, but I would.

A

B

Put it as one or two okay.

A

B

C

Let's put it as two for now for us and then you can readjust as needed.

A

Okay, does this one need Neeta enhancement, issue I, see a cab I, don't know. If no Zen has many issue there, I.

B

Think it's part of the broader projected service account volume, enhancement. Okay, so we can probably link it there. Okay, I.

A

See that this person is working on it, so I just put him as a job lead who should be the reviewers. Oh, come on you're already reading it right. So just put your name there.

A

Sure you're also reviewing it so I should put your name here as well Michelle. Do we also need to put their names like Jordan, their name here or no? This is just for yes, I.

B

Think it's fine to put down Jordan's name as the API, a peer reviewer or what I think he's been he's. I guess both okay.

A

Is that this right he's okay, do we need to add more people here? Was this good.

A

Alright, I will just leave it like this. For now the next one is CSI and she read only handling so Chris and it's the deb lead he's Chris on ice I.

C

Have not heard from Chris so I imagine he's not working on this. We might want to find a new owner. Okay,.

A

So just remove name anyone interested in looking into this.

C

The task here is basically go and take a look at the current state of read-only handling and CSI. There's already a bug open with some analysis and figure out. If there's any more work, we should do or not.

A

Okay, so we'll just leave it open for now, until somebody.

C

A

Okay, okay, next one is she related to you. Assuming warnings are my points, it says started, but we don't have a doubly tanco he's working at this I.

B

Know Jing was working on a couple of bug fixes around this area. hmm I can follow up with her to see if she, because she's able to continue working on it. Okay, so.

A

Should we put her name here or let's do just a question mark here.

B

Sure you can put chains name down.

A

Okay, so let me show you: let's do the reviewer array yeah, that's fine, okay!

A

So that's that is priorities.

A

And the next next one is three pause, so this is a Patrick Patrick used you're interested in working on this.

F

Very much so it's still a big problem for for anyone with local storage and I really would like to get that fixed. So the cap itself is I think mostly still relevant. We pushed it back last time because it was suggested to first address this issue with rescale.

F

It read rescheduling pods that is now fixed in 118 or will be fixed in our external provision of 1:18, and we can now come back to the TV if it is iron for increasing the chance that the scheduler actually picks a good node, where the pot can run the part where I'm uncertain is how to handle the femoral volumes. We have another line item here and further down about si.

F

Si si our formula volumes GA, but when I started thinking about this you've probably seen the mail on the ballistics George mailing list, I'm, not sure whether it's a good idea to really extend keep adding on more special cases to Oh si si ephemeral, inline volumes for a storage, capacitor tracking. We currently don't have a size field, for example, so my my current caps proposed to add that, but that's just another clutch on top of other clutches, in my opinion and I, rather would like to see it as reefing a bit.

F

What we do with si si ephemeral volumes in general.

F

So but they behave towards susi as I Drive a bit more like normal normal volumes. Yeah.

C

I think that's a really good point. You bring up I think there has been talk about whether we should make si si ephemeral volume, something more concrete and realistic in the si. Si spec itself today that we, the way that we implemented, is a little bit of a hack and I.

I

C

The alpha and beta so far, we've proven that this is a useful construct.

C

What do you think about that? It.

F

Is useful construct definitely I, don't see why we should need to modify the Z's I spec for it I.

C

F

C

Is that we're kind of violating the si si spec by the way that we implement femoral volumes? Yeah.

F

We can, let's definitely it's true, but the solution. If, if we just change, we see as I spec and don't change anything else we're in humanities. We still have all of the limitations of the current design. We don't.

B

F

Field in the API, we don't have any of the other features right.

C

So I'm not suggesting just making changes to see if I would I'm totally on board with kind of improving what we have today as well. Yep.

F

C

Maybe potentially both but I could be convinced to say hey, you know, let's only make changes on the kubernetes side. The effort to get this into CS I would not be worth it. I'll lean on you to kind of help make that decision. I.

E

Saw the food question: how is the current implementation valid CSS spec.

C

So I think Louis brought this up on the six storage mailing list at some point. I think the way that we use it, we Auto generate a random volume ID when we do a mount call. Basically, the node, publish, call and I think the spec implies that that ID should be something that comes from the storage system itself, that in this case there is no provisioning step.

C

So we kind of circumvent that and say hey if you're in a symbol, volume will cost you an auto-generated ID and you need to kind of you know, provision at mount time a volume and that's just it's not what CSI spec expected it works, but you know we're kind of just hijacking it and using it for our own means.

C

So it may be that we're okay with that, but it might it's something to kind of consider as we drive towards GA for this feature and I also agree with Patrick there's a lot of other functionality that we need to add. I think we were talking to Jen yesterday and she mentioned how or was a Michelle that we don't do.

C

The ephemeral storage capacity limits for CSI ephemeral volumes. We need to do that, just like we do for empty derp and so on.

E

Yeah, thank you.

K

Csi ephemeral volume is concerned is that using the storage, that's local on the worker node.

C

Si si ephemeral volumes are using local storage and their lifecycle is also tied to the pod they're, not persistent volumes if you're familiar with emptied our secret volumes that are built into entry.

C

Cfi ephemeral volumes are intended to have the same type of use case. Yeah.

F

But that's and that's actually one of the limitations.

F

The design is good for that purpose, but other useful use cases for it, for example, are pmm storage or just LLVM storage, but you bet that's provisioned by a normal size, I drove over a scratch space for applications right very easy to specify that an application needs force volumes if it can be in line in the pots back, because that removes all of the need for for higher level logic, for you know an operator which creates four volumes for specific parts, and all of that, so it's good. It's good good, API!

F

It's just to limit it at the moment, because it's kind of assuming that we paid volumes don't consume space, for example,.

G

Using real storage, who has a lot of volumes but I, don't want to put everything into one feature so.

F

My proposal is that we keep the CSI ephemeral volumes current design as it is, but we keep it in beta and the reasoning is that we just don't know yet how to do the other things that are ephemeral. Volumes in general would be useful for and therefore I think it's too early to just say we are done with this. We know that this is exactly what it should be. Perhaps we'll come back to it and may have to add for size field, for example,.

B

F

B

Also, we also cannot keep a feature in beta forever. We need to there's a kept open in sig architecture to sort of make sure that we are constantly still actively working on features and bringing them to ga-oh.

F

Therefore, my proposal is that we add another line: item below series I/o from volumes GA. Let's call it what generalized ephemeral volumes I still need to come up with a better name. That is not not not too easily confused with it. Once you.

A

F

Generic or generalize both works generic ephemeral volumes. The the goal has to be, in my opinion, that this works with a standard si si driver without changes in BC's, I driver or perhaps even any other storage system. It might even be an inline storage system that fits provisions of volume, but for handling for semantics should be ephemeral and it should be in line because that's for useful thing for for for scratch space. But you don't need to manage PVC separately from the pod, which uses it.

C

This sounds like a topic. We should have a standalone meeting to kind of discuss next steps and agree on what we don't do next.

K

I'm wondering why we can't treat locally attached storage on our worker nodes as storage, that we really ought to manage and actually allocate volumes for.

C

K

C

So you can use locally attached storage and do dynamic provisioning and everything you like through si si today as a persistent volume. It's the ephemeral use case that this feature is trying to tackle.

K

Right, so should that be an extension of the persistent volume infrastructure, we managed to do happily mean well treated almost the same and allow the volume can be either ephemeral or persistent.

C

Yeah I think that was considered initially, but there are ramifications of.

C

If we follow what we did in tree, then it makes sense for ephemeral volumes only to be defined in line not through the persistent volume infrastructure, because their lifecycle is tied to the pod. And so if the lifecycle is tied to the pod, having a object like a PV exists but the, but the underlying storage not exist because the pod was deleted would be very odd.

K

F

We have with different opinions about that. What's what's what's odd or what's acceptable, but that's dead. Let's have a separate meeting on that. Yes, I agree. So.

A

Should we have this item here and then just leave it for now and yeah.

C

Let's, let's keep it, let's assign it to Patrick and we can figure out later whether we want to remove it. Keep it I think we need to have some meetings to figure out the next steps in this whole area, yeah.

H

A

Just wondering how about this item do we want to put purchasing here as well just need to discuss together or work, or somebody else name, but this should be do.

F

A

F

Think we should not do it in GA in this cycle, because.

B

F

Not unless we agree on.

C

A

Know we're looking at this together right so.

F

A

Separate installation I think.

L

The real concern is that we need to decide if we want ephemeral volumes to go Ga before we finish volume, pools or storage pools, because if storage pools and could have monitoring the available available capacity goes betta with proper support for ephemeral volumes. Or if we come up with a solution for ephemeral volumes together with storage pools, then we can. You know we need to get a consistent design before fennel wines goes ta, so I.

B

Think that's a good point.

L

So if we can add a note to the storage pools line item also that there's a that this needs to have a consistent design with the femoral volumes or a replacement I.

K

Agree with that.

F

But that's why I came up with this generic storage generic ephemeral volumes, because the solution that was originally envisioned was to have a special extension for for a femoral volumes for the storage capacity tracking I. Just really don't think that business. This is right thing so, but yeah. Let's that's! Let's discuss this storage pool out here together with femoral wardens in in some upcoming meetings, I yeah.

A

We need to schedule, can you a Patrick? Can you try to schedule one meeting then we can start discussion.

F

How do you want to schedule that in in which calendar or.

A

F

A

Invite six origin we can we can. We can talk about that? Okay, okay, so this is design Patrick's. The deadly, sad, okay, yeah I can also help with the review of this one years. Well, so.

F

With the simplified plan for storage, pools and capacitor tracking would be to ignore ephemeral volumes for now it it would just be in alpha anyway, but I think that it's it's worthwhile to target some progress already now and I. Think alpha with the API as in the cap that is pending is mostly same, and we can just execute Efrain or volumes for now and make it make it clear, but this still needs to be solved before for beta. We.

A

Probably should discuss about this one right before we decide or you want to make this one author. We probably just what other well.

F

Yeah I actually well, we we did as good. We discussed we design already for the last side. Laughing yeah for this cycle would would make sense to.

A

Go after your try offer, we can try, you can try that okay, I.

L

Agree and and I'll just like put it out there I think the the right solution, in my opinion, would be to change the current a thermal volume support, because we we do have that gap with the femoral lines that they try to get scheduled on a host that doesn't have the capacity. Then then we have you, know: stock, pods, okay,.

C

Yeah, if we're targeting also, let's do these design meetings as early as possible, so we could hit that feature deadline. I. Imagine there's gonna be a lot of discussion here.

A

Okay, so, okay, so this one still two two is okay.

G

Yep sounds good to me: okay,.

A

So, okay, so that's fine! What a group I think it's! This is just design. I was only two scheduled review meeting for this one and so I think it's still just a design and I worked on it and Assad is Loki. The reviewer.

A

Next one CSI audit, we move and fast driver, so we shall this one. Is this already done? I thought somebody will have already been working on this report. Oh.

B

A

B

This is I think we're basically almost ready to release a image of the NFS driver. I think this will actually be able to be done soon.

B

The I scuzzy driver I need to follow up with the folks who volunteered to work on it to see if it's ready for release, seeing as well, okay and then for fiber, channel and flex adapters, I plan to deprecate those to be posts. Okay,.

A

Deprecated all right see do page.

A

So so we still have okay, so I'll have Michel listed here is thali insiders reviewer, so we'll just keep those looks good right.

C

Yeah, that's blank. Let's see if we can Michelle do you wanna, try to get volunteers for that, so.

B

There was that proposal to move out the NFS and an FS client provisioners.

B

A

B

A

B

A

B

Think it's it's sort of related to this. So once we get those two out and all the issues migrated over and stuff, then we can go ahead and external storage, okay,.

A

C

Let's break this item out into three items: one for moving out the NFS seconds, we're moving out Gloucester and then third for deprecating. You can leave it itself.

A

There's a glut classroom, I.

C

Think a cluster addition er yes and NFS provisioner.

I

A

Okay and then we should add another one.

A

The other one is that the sister FS is the Ganesha one and then there's another one. It's what the client.

B

There's enough s and edifice claw.

A

Okay, so though, so this is a Karen, sorry he's all right. Karen.

A

The first one is come on so who is working on the first one Oh humble.

A

A

B

You can put me down, oh, you can put me down for reviewing there and FS stuff.

A

This one who is going to review the Sun yeah hunt cluster as parishioner.

A

Humble will be the table eating okay, so the fruit. So this is this already started this. This one have not started hearing cluster. Is this one started.

H

A

What is the surgery level for this one priority level.

A

A

Don't you say the stock figs.

A

Is okay, so we don't really need that right so just say: never! Never!

A

A

Okay, so I think this mice, you okay, then they'll just leave Matt here, and you show us through the reviewer for this application of external storage.

A

Next, why is the volume and snapshot namespace transfer? Mike? You still working on this. You still the tablet for this one Mike. There.

A

mmm Looks like she's not online.

A

Okay, so he has a cap.

A

Does anyone know, let's.

C

Leave it aside to him for now and then we can reconfirm in two weeks. If he does not want to work on it or is not available, then we can try to find another owner. Okay,.

A

All right so I was still so sad. It was to be the revealer. Oh yeah,.

C

That's fun: okay,.

A

And then this is a design and then the priorities number three: it's okay, yeah.

C

I think that's fine, okay,.

A

Okay, next one is okay: what in house yeah so this one? We are I, think getting close to get the CSS back in then we will continue what kind of so this, yes, so should still be alpha, because we we get a caffeine last time, but we have not finished implantation. So it's still alpha Sonique is the the tab. Lead me show myself be reviewer yeah, so I think this is fine, we'll just.

A

Leave it like this.

A

And the next one is generic data generically the popular data source.

A

Is it okay, so I thought our far we just go to bed on? Oh, is this the targeting data in another 19 I.

C

Don't think this? Oh yes! Yes, that's right, because we.

F

C

The Alpha in the last quarter and alpha was just removing the feature gate targeting beta is fine here. I think this is going to be a huge project, so I'm not sure it's going to make it, but we can try. Okay,.

A

But we can go directly to beta, because basically we don't really have any code written for alpha ray I mean we open the city gate.

C

I

So then, then it's told the right person yeah.

A

C

He's not online but I think he's the right person to work on it. We can confirm next time when he's available. Okay,.

A

All right so sorry osteo the review all right, yeah.

C

A

I'm, just storage, API, oh I, think we probably go change it early. I think all of this end status should not be. Should we also move everything? Maybe that doesn't matter it's the end status but okay. So this one I see that there are design meetings every week so Jeff you are still the wt4 this for Windows.

M

Jeff actually lost power. This is John Cove.

M

Yeah we're continuing weekly meetings and refining the API and right now we're working on what we might think. The G RPC interface will look like to propose at the next meeting.

A

Okay- and the answer is Joe- the reviewer and Joe has me reviewing right.

M

Correct: okay,.

A

So we leave that there is this still tugging design for 119.

M

Yeah I think that's okay,.

A

All right, so number three is okay. Three is okay: priority I.

M

Think I'd leave that up to the leaders I'm three scenes right: okay,.

C

A

So, oh this one I didn't ask what this one is: okay to do the sauce yeah.

C

That one, okay and.

A

The next one is a warning station for a stay for said and I thought. The KK said he's going to work on this. One in 1.19 are used to interested KK. Yes,.

F

A

Have you checked the Wiz I think it's a king ovince in sick, ABS, I didn't.

J

Get a chance yet: okay, okay,.

A

All right so well just put your name here: yeah.

A

Sure is a peer reviewer. We should need to have somebody else. Is she the swampy himand is warning station come on? Do you want you to view this one? What an expansion of stable set? Yes,.

E

A

And the next one is PVC Christopher said, would not be Auto. Remove, don't know today was day. Buy you a line, it's probably not in a call I will check with him last so much everything he said. He's interested just do that. Won't you ask him if he's too interested in this human doll 19, so just keep his name here. For now, so I can still be reviewer and.

A

So this is Joe 3 and the previous one is also 3 and the next one is ok. So we have those euros you will have yuto's month. Ok, split it into a new repo who added us me shower yawn, who I did this one.

B

So this came up. This came up in sig arch, inelastic, arch meeting. Basically we in 117 we move the mount library out of the kubernetes repo into kubernetes util and in 118 we had a number of regressions happened due to changes made in the the other repo that was not caught with quickly, because we don't run, we don't run windows builds. We don't run e to e tests against these changes, so the ask from sig arch is to so.

B

The other problem is that this kate's utils has a lot of other things besides Mount and whenever we have to cherry-pick a fix back to update the new Kate's utils dependency, we end up pulling in potentially pulling in a bunch of unrelated changes. So sig arch wants us to revisit this, pushing mount library out to Kate's, utils and sort of think about a better way to be able to isolate the changes that we make and also have better testing for it, so that do they suggest you have the seen its own.

G

B

Yeah one suggestion is to just have it in a new you, like Kate's, slash, mount utils repo, something else I was considering, was moving it back into staging there's. There's a couple options: I think we'll need to sort of investigate it.

B

I guess you can put my name down I'll work with sig arch to kind of figure out. What's: okay,.

A

C

If anybody really wants to touch a lot of the core code and move a lot of the core code around, this is your opportunity right here. The mount library is used by all of core kubernetes and a lot of the CSI drivers, and so anyone who wants to really get involved with the kubernetes code. This is your opportunity. Travis worked on this last and I think it would be a good experience. So, if you're interested please reach out to any of us and we'd be happy to have you work on this.

A

Okay, so who should be the reviewer? You.

C

Can put me down.

C

Sure yeah put you on and then you can put me in the middle column. Okay,.

A

Next, one okay, so we already talked about this two FS groups for in CSI design; okay, so who added this item probably work on this? Oh.

G

I edited it and I'm hoping okay.

A

Cool I'm, sorry cool will be oh, come on. You want this.

A

Yeah all pressure very young, put us there reviewer then. Yes, so good, okay, okay, so this might be a design right. So so this will be just the CSI apart, there's no other design just to CSI design.

E

This is this: will try to do this implementation? Actually, okay,.

A

So we so we use the design. Was it off our? What is the I.

E

Think it'll be alpha will have to make a change in CSI driver object, so it has to feature gated but yeah. Okay, let need a cap. We just discussed this morning to to solve this.

E

A

So we already talked about integration and then there's this immutable secrets and config Maps.

B

This, yes, this is an effort, that's driven by six scalability. Oh boy, tech is the owner for this I believe Saad. Have you been be viewing this one.

C

We're talking about in beautiful secrets and config Maps, yes, I have yeah. You can put my name down.

C

um I need to jump out for another meeting through the shingle. Let you carry on sure.

A

Okay thinks that okay.

I

Breathing yeah.

A

I think this is already. This is the last item and we are at the top of the hour. Are there anything else anyone want to you? What do you add I.

A

Think that's all we have for today's meeting. If there are no other issues to discuss, then that's it for today thanks everyone. Thank you. Thank you, bye. Thank you.