Kubernetes Storage SIG, 11 Oct 2018

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes SIG Storage 20181011

Description

Kubernetes Storage Special-Interest-Group (SIG) Meeting - 11 October 2018

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

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

Moderator: Saad Ali (Google)

Chat Log:

09:12:37 From Sig Release : I am going to drop off now. Thanks all
09:26:56 From Deep Debroy : This is the feature for CSI migration: https://github.com/kubernetes/features/issues/625

A

All right today is October 11 2018. This is the meeting of the kubernetes storage special interest group. As a reminder, this meeting is public and recorded and published on YouTube. This is our agenda. Doc, it's linked in the calendar, invite feel free to add any items to it, specifically any pr's that need attention or design reviews or anything else that you'd like to discuss today on the agenda. First up we have. I am I pronouncing that right. That's.

B

A

Sig release to say a few words to us: go ahead. Hi.

B

um So basically, I just wanted to drop by and use myself for folks who haven't we have for whom I haven't introduced before so I'm. The 113 release lead and we are basically meeting up a different six to talk a little bit about the timeline of the release itself and- and we are currently in the enhancement, collection phase and so discuss a little bit about what each cig is planning for the future load for 113 itself.

B

So 113 is like a super short release by now I'm hoping most of you would have seen the schedule itself cope freezes on 11:15 and we are planning to release by 12:00 3:00 before the Seattle cube con, so which basically just leaves us about six weeks or so for development itself. That is, code testing and talks to wrangle all of them in so so we started the enhancement collection on Monday, and currently we like yeah, we are seeing close to 11 enhancements on storage.

B

So, given that it's a super short release, I just wanted to get a sense of how you feel regarding the sense of all these features to get into 1:30. And, if not just in creating this. If you make a call by enhancement, freeze which is the 23rd of April yeah,.

A

That's good good feedback, I think our biggest goal. This quarter is to try and get CSI to 1.0, and then there is a number of other features that have been pending, that we want to kind of move, move towards beta or GA. What we're gonna do is reassess as we get closer to the 23rd. How many of these were actually going to be able to land within time, yeah prioritize and cut the ones that we can't and focus on the items that are absolutely critical, critical to get us to CSI. One point: oh yeah.

B

That'd be great and along it along the way, if you could I know, Kendrick had left to come into Kendrick assigned is our enhancement seed, so I think he's left a comment on most of those issues asking for water spend if it is graduating like is a test or code or talks. If, if the feature owners could leave that information, there that'll be super useful for us yeah.

A

If you have any of these feature issues assigned to you, please take a look at them and respond to any comments. There.

B

That's all I wanted to just drop by and say hi awesome.

A

Thank you so much and next step is our q4 1.13 update, so we're gonna go over the planning spreadsheet for the items that we have tracked again. This is a much shorter quarter than usual. So if you feel like you're not going to be able to finish an item within time, it's okay to get it punted to the next quarter. So let's do a quick status review and get any updates from folks. First up for CSI, we have blocked volume, support moving to beta Vlad. Are you on track for this?

A

C

That that certainly looks like is what happened: cool.

A

Yeah, it's already work already. You started on it.

C

There's a PR pending somebody I can't remember the name he's doing some some refactoring and which is based on the port of our DB. Stop looking for block so I'm using that as the basis for anything that needs to be fixed. So I've been working on that with him or her I'm, not even sure, and that will be the basis and then I also have Chris testing some stuff as well. To make sure that everything looks good. So.

A

C

Switch it to beta cool.

A

Thanks bud so we're going to flip over the CSI drivers and get a status update on those at the end of the quarter. I spoke with some folks from the VMware team and looks like they're targeting the December timeframe, CSI library moving the mount library from core kubernetes kubernetes to an external common repo travis. Any updates on this.

D

Yeah I've gotten some feedback on the PR that is open. That I need to incorporate right now, so it is definitely started and I have much more bandwidth to work on this now because I have been pretty slow on it. So apologies for that, but yeah. That's my attention and I'm heading towards the next steps. Awesome.

A

Could you place the PR in this column over here, yeah I thought I'd done that before, but yeah I will do so awesome. Thank you. Next up is a pluggable into n test framework, something that is being led by Patrick Patrick. Are you on the line by any chance.

A

Brad, do you happen to know the status on this.

E

One's been working on this and yeah I mean he's digging it cracking into it right now. I, don't think we have a design, doc, yeh, ok,.

A

E

Definitely in progress, cool.

A

I do want to call this alpha or designed for this order.

E

We can call it design. Our ambition is to actually have some work done, though. Ok.

F

G

And actually I'm also doing some work in this area as well to refactor some of the tests that we have and I think we're planning on using the PD CSI driver as they can you Pig to test out some of this.

A

Okay, that would be excellent, Thank, You Michelle, and thank you, my Faison and Brad, for the updates on that. Next up is the kubernetes conformance process starting to implement that 3 yeah.

H

Hi, this is Jenny actually I haven't made any progress on this, yet I have to get started. I promise that I'll get going.

A

Problem. Thank you. Next up is provisioning capacity reporting for a generic topology, which is required for local volume, dynamic provisioning, Michelle. Any updates on this one yeah.

G

We've just been sort of brainstorming some ideas on possible designs, we're kind of we have like two basic designs. One is like generic that can work across many different kinds of topologies, but it's pretty complicated and involved.

G

We're also trying to consider possible designs that might only be limited to local volumes as right now we don't really have use cases for other volume types got.

A

It okay and the the coldest quarter is just to design it, so it sounds like it's on track.

A

Next, up is CSI external containers moving leader election to the least object. This is a recommendation from Jordan Matt. Any updates on this.

A

You happen to know if Matt's working on this.

E

Yes, he is working on this awesome.

A

Thank you. Next up the sub path, expansion. This is a p3 cap. Taylor mentioned he was going to work on it. Yeah.

G

He actually has a. He wrote up a little proposal for it. I have not been great at finding time to review it, but I will try to do that sometime this week. Okay,.

A

And if anyone else is interested in helping review, that proposal feel free.

A

Next up, is you see a side driver, we're gonna, ignore that then we've got the I scuzzy common library, moving towards g8 John. Any updates on this.

A

As John Griffith on the line or he's been on the line by any chance and able to get enough, I'm.

I

A

I

Yeah sorry I missed this part of the meeting last week. I had a conflict, so I've I've reviewed this and I.

I

It will work, I think to get it to the state where a lot of drivers will want to use it. We need you no ill need to get a lot of features in testing. So my concern with this was without a good regime for testing it I'm kind of scared to just start throwing pr's at it to try to add the features that I think are missing, but I mean as a baseline. It's a good starting point. It sure is almost all of what cubelet currently does.

I

I only noted a couple of missions and I'd be happy to write the PRS to do those, but you know we kind of need to get it launched and get a get a testing regime in place. Okay,.

A

So maybe we get those initial PRS merged and then focus on getting some sort of testing framework going and then from then on start focusing on future improvements. Yeah.

I

That would be my suggestion. Okay,.

A

Seems reasonable.

J

Hi, this is a shame and I. Think I have take a look at that PR and realize that that the way is using have to require the share the network name space with the host. Otherwise, you cannot run the ICRC, for the mean cur container. So is that is that desired or well.

I

It's if that kind of thing isn't desired, but I've never found someone that had a good workaround for it. So if you can find a way to requirement.

J

I

J

Well, we spent quite some time and tried you look around this and yeah. In the end, we use center to get to the hostname space and ask you, sir. So first we require user to installed my Scottie to me on the host. Instead of restoring the container as I can do we use it as introduced which namespace back to use that binary on the host. So then we multiple containers and share the they share. The library yeah.

I

Another bit something similar: we actually have a shared amount and we we just route into the shared mount and run everything from there. So yeah.

K

I

Some sort of scheme like that is required because there's no way to do everything guys because he needs inside of a inside of a container. Yes,.

J

And also, we cannot install the ICRC sea and ice cuz it may inside container, because, basically, the kernel names, the net link used by the SOC of the main talk to discuss, be doesn't support namespace, yet in the kernel part, so County around one instance of ice gossipy in one node. So we prefer that one to be on the host rather than brownie, on something.

A

Okay, so maybe you take that feedback to the PR and possibly not or a blocker for the initial PR, but a follow-up enhancement.

J

Yeah I already come the piano man perfect.

E

It's documented those issues, yeah.

I

I was gonna, say we should document how to use the library so that when people use it, they understand all the other requirements that are necessary for the environment to successfully use the library we.

E

Would like to, if possible, you know if we have to change. You know proposed changes to the curl or whatever to get this, something that can run in a container. You know we'd like to do that. Yeah.

J

E

Know you would need big.

H

J

Wait for probably two years to get to the main screen: I I.

I

Don't think it's the I, don't think the kernel is the problem. I think it's the user space tools, both the I scuzzy daemon and there's also the multipath daemon. Don't forget that one I think.

J

Is a problem? I have referred to one get used to my comments on that. Pri have referred to one link it back to another. One Google Group is bashing about this issue and the it's the kernel, I think it's the kernel saying, because that somebody confirm that and I also try to look into the common codes to see that I think it's. The kernel quote.

I

It we should have a plan to pursue making things better, but in the immediate term the strategy is, you run the demons on the host and you play games with the container to connect back to the demons on the host yeah.

J

D

The works yeah.

E

Okay, I mean I Alta. My goal right is to get all those drivers containerized, just cuz. We have read-only hosts now, and you know stuff like that. I and I'm gonna say that this is gonna, be one of the few that we can't containerize, which is going to make it a little bit awkward. This.

L

One is yours, can be containerized, just fine, it's just the they have to have access to the tooth to the host demon. Like that's.

K

E

L

Big issue: okay, everything else can be containerized. What.

E

Happens if the demon runs in the container right.

L

You just have to kill the host demon.

K

L

Can you can run the demon in the container and there are examples out there of how to do it, but you can't run that with the host also running the demon. Okay,.

E

Okay, so we could shut off the host daemon and then just run in the container. If we had yes correct well,.

J

E

J

Don't know that's because you know the banku ship with the I Stassi. Oh my Scottie train stored in oh, it's servers and yeah I. Think it's more feasible to require you search in stored on. We.

I

Need to document what actually works and what the deployment options are. Yeah.

L

I

There there are many ways to do it: they're.

L

I

L

They're not very pretty and the containers that are running like C, so you do run a nice kzd in a container. It requires it's almost like running it on the host. It has to have so much access.

M

On the same host and they cannot each load the demons independently, so yeah.

L

The demon would have to be running its own separate container from any of the plugins, and then the plugins would be running their own versions of their own I scuzzy, a DM or at least accessing the hosts I scuzzy ad I'm, depending on how you want to do that. But all of those I, scuzzy, idioms or tooling, then access the singular.

K

A

One point of feedback: are we okay calling this GA, or should we change this to like alpha or beta or something.

E

So we have these other issues. I would.

I

Not call it GA I'd call it alpha. I mean you want people to start using and giving feedback yeah.

A

I

A

Anybody disagree.

L

No I alpha make sense to me. Okay,.

A

Alright and let's take these issues to the actual PR and the repo there's, a separate new repo for I scuzzy common under kubernetes CSI, so feel free to open new issues there and carry on the discussion there.

A

Next up is the CSI spec we're going to try and add dynamics max capacity per plug-in per pod, sorry per plug-in per node count. This is work that amant is leading along with following an expansion. Come on. You want to give an update on this I'll.

N

Open it, beer for the max capacity for the CSI I have updated, updated the PR for obviously it's for the for the volume expansion. Currently, the it is, the CSI volume expansion is stuck in. Basically, a wording like whether to like, where to call it like online, is only for controller expansion or is it like also covers tech volume that are attached to the node wire, some sort of like node publish a node stage like I scuzzy, so it's basically a wording thing that I need to sort out for wall expansion, okay,.

A

Sounds good thanks month the CSI drivers I'm going to skip over and talk about beginning implementing the migration off the entry driver to see aside David. Are you on the line.

O

C

O

Think it started on getting the translation library set up. So that's going to be like a foundation for the rest of the components and we have like a weekly sink set.

K

O

Of go over the rest of the items.

O

So the translation library is meant to do the necessary translations between the entry data structures and the CSI.

N

That makes sense.

A

Work I imagine this might be one of the items that we end up. Slipping.

A

Alright and if you're not speaking, please mute, your mic is.

G

There also a feature issue for this: I didn't see it in the list earlier release.

A

Team was tracking yeah good point.

E

Well, you're, looking sad for for CSI 2ga, we don't really plan on moving any of the plug-ins out of tree for 1:13, okay, yeah.

A

Yes, for a CSI GA, it's just independence of the migration, getting the actual mechanism for CSI in place.

E

Because I imagine it's gonna be a multi-step process right, even when we release the CSI driver. You know we'll have to let that sit out there for an alpha beta and then then look at actually migrating it, probably one by one yep.

A

That's that's the plan.

A

Next up is CSI external provisioner topology support for kubernetes CSI. This is work again. Deep is working on with Shane yeah.

O

It's been started. We have identified about three or four sort of well scoped out items. They include things like making sure the stateful set deployments are well spread out through everything, as it's done in the entry, as well as a couple of things around using informers for the CSI node info objects, and things like that. So this Devon scoped out I'm working on the first one, should have a PR up by hopefully under feet, cool.

A

Thank you deep. Next up, CSI driver update at fibre channel driver to use library.

A

Is this still work? That's going on.

P

Yeah, it's it's official fibre channel driver, but I haven't really been looking at it because I've started looking into the ete framework stuff. Okay,.

D

P

For the fibre channel, libraries I think I'll make a PR to get it moved into the community CSI repo that was just made increasingly.

A

Cool, so the second item here is the fiber channel common library, so you're saying that it doesn't need a permanent home now, so the repo is created and PR.

A

A

Once that's done, do you want to also update the fiber channel driver to use the library this quarter? Yep.

E

A

Cool so I'll leave both of those there. Next up is how to test these different fiber channel libraries or fiber Chinese drivers that we have fiber channel I scuzzy and the library's NFS I scuzzy fiber channel I think this goes back to what Ben was mentioning. We have these libraries. How do we actually test them and I think that'll be an important next question. Any updates on this from either Brad or Ben.

E

So this goes into the word. My solution is doing to break out some of the end-to-end testing. You know, there's like 15 pieces, I. Think thing you know they'll make up this one particular thing and it's in progress I mean we. We intend to have something out, I, don't know in the 113.

E

We'll definitely have the refactoring done and then we're gonna start looking at some more engine tests and I wonder if we should get rid of like the testing of the fiber channel ice, because the NFS in three libraries and just do the CSI pieces of this.

I

We don't we don't want to have regressions on the entry stuff, so you can.

Q

I

Them but but uh yeah, please invite me to any meetings you have on this subject, but I think once we have tests, you can run externa externally and then test it'll just be a matter of doing some ordinary kubernetes and and testing using a driver that includes with these libraries yeah.

M

I

That you exercise all the bits and if it works, that's a pretty good regression.

A

That seems reasonable. Okay,.

E

Oh I'll set up recalled by next Tuesday of next week. If that's okay, bane to talk about this yeah.

I

As long as it's not it noon, eastern okay.

A

All right cool next up is flex resizing support. This PR was already pending last quarter, so it should be pretty close to getting merged any update on this.

F

I I spoke to him and and Chuck Reed via slack. Both of them indicated that they they would review it this week. So I don't know if a mentally are on. The call is that still okay or yeah.

A

That seems reasonable. We've got plenty of time, sir okay. Well, thank you.

A

Online volume, expansion to beta a month and Matt is still something that you plan to do.

N

Yeah I think the PR just missed by a whisker, actually there's already a PR open so which is need to like maybe revisit but Matthew they're right. Oh.

A

That sounds like most of that is just done and needs to PR just needs to be reviewed. Next up is no shutdown. Node failure handling pod not deleted when shut down reducing recovery, time, big issue, Jing or Yasin. Any updates on this.

R

So I'm, currently and I start working on some proposal and I. Think I will contact Jesse and Nick to like about it proposal and- and we can share with the six alright yeah okay, so we need. We also need a feature for this, or this is more or less like now.

A

You can consider this bug level I mean I, think it depends on what the actual proposal ends up being but and get away with. Calling this bug. Louisville. Okay, is apparently already a feature. So, okay.

R

A

A

K

A

Already a feature here that we could potentially reuse if we decide that we still want to do this team mm-hm.

R

Okay, okay, that's good, then yeah I will I can start working on the proposal. Yeah! Okay, if.

A

You intend to use this, please make sure to mark it as 1:13. Okay, just currently its mark 112, all right next up is bringing topology to GA Michelle yeah.

G

So I think the main work that's needed left is just to add a few more test cases other than that it should be ready to go cool.

A

And local PBS.

G

This one I'm less inclined to move to GA, okay,.

N

G

Think there's still some questions about overall lifecycle, so I would be open to having another round another release of more feedback on end.

A

And just cut it for this quarter, then considering it is a fairly short quarter.

A

Could you update 121 to move it to next quarter, yeah.

G

I think it's it's.

A

A

Okay, cool next up is.

A

Revisit design for local attached limits, I think there was Tim had some concerns about this design. I think we discussed this with him offline and he was interested in making this more generic any on this. On my different mom or Michelle,.

N

No I think we need to maybe bring this to six scheduling and get their input actually, because anything we do for the general, like, though, the.

Q

N

Counting will have to.

Q

A

Q

The proposal that.

A

D

A

Up with, are there discussions with you on on it, and it sounds like that way.

D

A

Next up is volume attached limits, integration for delayed, binding, deep, that's.

O

Kind of tied to the item above so it's probably not going to be done in this order, because we've won the design to be fixed up a little more.

A

Okay, are we safe to just cut it for this quarter, them I think.

O

So, okay, ready Michelle, yeah.

A

I'll go ahead and do that and then can someone update five five four to ensure it's not in 113.

A

Continue working on snapshots, shame you wanna, give an update on this yeah.

S

Sure so we happy ours on deletion policy and admission webhook for the deferred snapshot class. Those are in reviews and we also have a CSS back on topology for snapshots. That is also in reviewed and the final laser is working progress. So there are three finalize errs the first. You are on vol snapshot and wanna snapshot content, so those will be added to the central controller and then the third one. We want to add that on the wall rim, so probably PVC, we delete when we delete the PVC.

S

We want to check whether your the snapshot being created from that I'm wondering whether we should add that to the the external storage controller, because it seems like the this. The controller under external storage is the right place, adding that, but that means extremists story will be dependent.

S

Voting snapshot, the extra no snapshot, which seems to be weird so this boundary anything okay,.

A

Let's take that up in the CSI meeting and talk about it there sure, but it looks like solid progress here.

R

Just one thing is resource code: I won't be able to Eddie yeah because that ser de resource code on got.

A

It that's okay, I think, there's still solid progress being made there.

A

Next up is automated end-to-end testing of the CSI side. Car containers before release both major and minor Patrick is looking into this.

A

And he's not on the line to give us a status update so we'll get that from him next time. This.

G

Is also something that we plan to do for the PD CSI driver, but I guess this item is more about testing like mock drivers right.

A

E

We saw Patrick I want to say it's been like four Sigma Z. He.

A

Shows up to the CSI meetings? Okay, because timezone is different.

A

Next up is moving the CSI spec to 1.00. This is still on target.

A

Next, up is moving CSI, persistent volume, source and volume attachment objects to be. One is Shawn on the line.

Q

I start it right.

A

Q

Question is what should I do about those CSI peripheral bullying source, because this isn't core we want. There is nothing to do about it. I think I.

A

Think there might be a comment on there if I remember correctly, that says it's beta other than that.

A

Yeah, you can go ahead and check it yeah beyond that. Nothing! That's a next up is the cubelet device plug in registration mechanism, so Vlad I think we need to get the conversation going here would be device plug-in folks and make sure this is on their agenda right for q4. Let's get this going, ASAP, okay, because it kind of depends on outside of this group, and we want to make sure it's on their roadmap.

C

Absolutely I'll follow up with them cool.

A

A

Next up is the CRD installation mechanism.

A

We have a number of new CR DS that the core is going to depend on CSI driver object and CSI node, so object in the Alpha releases that last quarter. These objects, the CR DS for them- need to be manually installed, that's inconvenient. We want this to be automatically installed. The feedback from API machinery was do not use the controller students to all this. This quarter to unblock ourselves. What we're gonna do is use the add-on manager to pre installed CR DS.

A

We went to API machinery yesterday to ask for feedback on what the best way to resolve this was, and they said to follow up with sig cluster lifecycle. So I have something on the agenda with sig cluster lifecycle and their next meeting to discuss this.

A

In the meantime, I'm going to pursue installation with add-on manager and that should be sufficient to block unblock us and whatever sake cluster lifecycle decides to do, can be the wrong long-term solution and there's also a number of issues that come up with using a CR D in the core, including things like race conditions. If the CR D is not installed in things like the informer, what happens if the CR D is deleted, while it's in use things like that, and the recommendation from API machinery was, if anything is not behaving as intended.

A

Please file bugs against API machinery and they will look at them and help fix them, but in general, their feedback is that the components that consume these CR DS should gracefully handle the non existence of the CRD, essentially treat it like a somebody flipping a flag to disable the feature this becomes complicated for us, because traditionally we make an assumption about whether a feature is enabled or disabled at the beginning of a binary initialization, and we don't expect that to flip-flop during runtime, whereas CR DS could potentially flop during runtime, they can get deleted and we need to handle that gracefully on our end as much as possible.

A

So that will continue that work will continue.

A

Next up is moving our back roles, definition from kubernetes kubernetes to external repos. Luckily, patrick has agreed to help with this as well.

A

We're going to follow up with Jordan to ensure that we're ok, deprecating the entry code and if so, we're gonna go ahead and move the role definitions to the external repos. Next up is moving the CSI driver and CSI node info objects from alpha to beta. This is blocked on the CR D installation mechanism, so no update there.

A

Next up is implementing CSI pod inline volume support when there Vlad I think the PR that you have. You are starting to move forward. Yeah.

C

I've started to move forward in my plan is to get everything stable this weekend and have a start moving toward creating a demo. So I can finalize the the PR and start having review as soon as possible. Awesome.

A

Thank you and in terms of priority, this is definitely a p2 compared to the cubelet device. Plugin registration mechanism- that's gonna, be a blocker for CSI 41.0. So let's make sure to get that unblocked as soon as possible.

A

Next up is PVC namespace transfer, targeting alpha Jun I, don't think is on the line. Does anybody know the status of this.

A

Okay, we'll get a status update, hopefully next time on. Next is data population supporting data source, the other data sources other than snapshots for cloning, we'll follow up with John on that next time. Both of these are p3 ability to say sorry.

T

We've been working on that and testing things out for the transfer. We've there's a possibility that we can just update the claim ref to move it to a new namespace and PvP in the other namespace. So John was gonna, submit that since I broke, my github account and had to open anyone, but we will get that at least on the calendar, so everyone can start reviewing it. That'd.

A

Be great all right cool, so it looks like this work to do. The namespace transfer is in progress and possibly as PR soon and.

T

I did talk with Jordan separately about it to make sure what we did would be acceptable from a security standpoint.

C

T

There yep yep he he kind of had like four criteria that he felt like me and to be met. So we made sure that it tracked against us nice.

T

We don't, we just have a Google Doc. We need to reopen up TR, I, switch computers and didn't disable. My two-factor authentication with github and now I have to open up a new account.

T

John was gonna, go ahead and just submit it with github. Id I'll still go back with him by the end of the week and see you know if we get a PR out there sooner than later, yeah.

A

If we can get the PR and the design doc that way, folks and start taking a look at it, that'd be great. Next up is the ability to set UID on volumes in addition to GID, Almonte I, think you're tracking. This many updates sorry.

N

What was the Oh.

A

Uid GID, oh I,.

N

Have a star on a kid actually: okay,.

A

No worries and then we've got a couple of bug, fixes here: CSI side to our container splitting up driver registrar in two separate, repos, I, don't think I don't know if Lewis is on the line. The weeks.

A

So I don't think he started work on this. Yet from my latest meetings with him improving dependency injection for volume plugins.

A

Does anybody have a status update on this or a summary of what it is I think I might have missed it.

Q

Take a look at this real, quick.

Q

A

Okay, this is I, think cleanup for communities, kubernetes volume code, so good to do well. Chang, are you on the line yeah.

K

A

You want to talk about this yeah.

K

Just general don't clean up for like there is a lot of because annoyances that comes with the current, like a lot of the dependencies, are injected plugins through the volume host interface and every, for example, that ever you plug in X, is expected to check nil its own code, which is more error-prone.

K

If there is one generic way to and.

Q

The other, the other issue is.

K

That there's no good way to see which plug-in depends on what and I don't think every single plug-in depends on every single one of those items in the volume closes yeah interface.

A

Is a really really bad piece of code? I think there's been multiple bugs open to clean that up for a long time. I, don't think, we've gotten to it if anyone's interested in working on that, let me know, but considering its a short quarter might might might not be the wisest use of time for, for this.

A

Currently, it's unassigned, but if you're interested in speed jump.

A

Next up is mount options for CSI yeah. This.

I

Is this is work, I did back in 112 and then I got stuck on the dependency stuff, and so it didn't make the deadline, but I just need to write the unit tests. This is this is essential for NFS. You can't really do in a festival without mount option, so okay, men options into the sidecar and and into the kubernetes CSI driver mount option, support there. So there's actually two PRS here: I'll, take it the other one. Okay,.

A

And that's gonna go into external.

I

This PR yeah goes into the external provisioner and then there's a very like a one-line change to ticker renée's itself to say yes, we support mount options in CSI, also I think yet not passing the mount options like yeah yeah, so my peer will fix that. Okay,.

N

I

Haven't pushed the latest version, so this is an old one, but a.

A

I

Fixed amount options well.

A

Hammad, can you review this code yeah.

N

A

You alright, so we have a lot that we're doing in a very short amount of time code freezes a little over a month away. The 23rd, as ash mentioned, was the date that we need to officially finalize on the feature repo what what we're committing to for this quarter. So when we have our next meeting, let's reassess what we think we can make in this quarter and what we can't on it's: okay, to say that the quarter is too short and that we don't have time for a specific feature.

A

Let's focus on delivering quality rather than trying to get quantity of features in, and that's all that I have today. It doesn't look like there's any PRS or designs that need attention at the moment. Anything anybody else wants to discuss or bring up. I have a good question.

U

Sure so for the CSI driver release for 1.13. Do we need to create a issue in the common area? Slash features so that I don't see any drivers being tracked. Yeah.

A

Now the drivers are just going to be tracked internally within the sig. Essentially they are external to the core of kubernetes kubernetes, so they don't need to be tracked and kubernetes features. Gotcha.

U

A

It's not anything else.

A

Let me take a quick look at the chat window. Okay, I think we are good. Thank you very much for your time and we'll reconvene in two weeks time. Thank you very much.

T