Kubernetes SIG Release, 26 Mar 2018

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes 1.10 FINAL release burndown meeting 20180326

Description

http://bit.ly/k8s110-burndown

A

Welcome everybody today is Monday March 26th 2018. This is the kubernetes 1.10 release team burned down meeting. So if that's the meeting, you are looking for you're in the right meeting. If that's the meaning you're not looking for then you're, not the right me I'm, your host Jay singer Dumars, and if you want to follow along after the fact, the meeting minutes are available at bitly, slash gates, 1, 10, burned down so without further ado.

A

Today is the hopefully final release team meeting and we're gonna talk about signal and issues and all the good stuff that is necessary to make sure that we are going to release a healthy, happy bouncing baby kubernetes. Today, after a three month, concerted effort by a team of experts and specialists and wizards and sorceress is and the whole team here. So I yeah you've left out left shocks there.

A

This release has definitely been brought to you by left shark and I'm, not gonna, not gonna promise, but there may be a left shark themed, kubernetes t-shirt, going to all the release team members and special mentions as well. So so I may be asking you for your t-shirt, size yeah. So here we go. I I'm gonna share my screen and complain about it like normal. um Let's see.

B

A

That is visible to everybody. Yes, so release de mechanics right now. The thing that needs the most attention, in my opinion, is release notes. So we can get all hands on deck to help Nick sort through these things. Nick. Do you want to go through these real, quick.

C

Sorry I had to find my mute button. Yes, I would I would love to go through these real quick, so Caleb has asked that we add in the external dependencies, but I, don't know what they are or where to find them. So if somebody does know the answer to that now, it would certainly be helpful. Do we have anybody who can answer that question?

C

A

How how does one even find these things? That's what I want to know. I'm.

D

In the way way, back I used to scrape them from CI logs, which is pretty terrible, which is pretty terrible, yeah right, but you should be able to ask for the container runtime support. You should be able to ask, say node for CNI. You should be a plastic network for a TV version. You should be able to ask API machinery, oh yeah,.

A

This has to be done today in like the next three hours.

C

I have a question: are you trying to say- and it sounds like you are, that this is not documented anywhere.

D

Not to the best of my knowledge, but my knowledge is always very limited to be how one for the previous release at least yeah yeah at the bottom of the release. Right.

E

Here's the previous two releases is that this section has always been well. Okay, for the previous two releases, I'm very much a yellow thing. Content comes in god that doesn't come in not well addressed. Okay,.

C

So I'm gonna do the best. I can well.

A

We can I guess just search the commits for those things, I suppose yeah.

C

There are some there are some release, notes that mention you know, such-and-such upgraded to such-and-such, so I might be able to find some of those that way by basically working from one nine, so okay, so I will do that. And then, if we need to kind of I mean look, the the SIG's are gonna respond to you Jase much more much more quickly than they're gonna respond to me. So I'll, let you know you know who needs to be know right strangled, so we'll go with that. Okay, so that's that's number.

C

One number two I need some clarity on persistent volume, resized versus volume, resize I got a I, got a comment from Nik Ren that TV resize did not go in to 110, but I have release, notes that say: volume resize went in to 110 I, don't know enough to know what the difference is between those two things.

A

So Michele offered to help in the slack channel.

C

A

Ping, her privately in a message and ask her to do a brain dump. If you could and text and then word submit that into the.

C

Okay, Jennifer's gonna help on the PVC section.

E

Let me let me just add here: if Michelle is gonna come in and and help out, you might want to ask her I'm looking at that content right now and my brain is falling over, because this is looking like bits and pieces of things that I was told, went in, but they were buying the alpha gauge and it's disabled, so we're not documenting it and we're not telling anybody about it and bits and pieces of things that didn't go in or maybe I'm even mixing up features at this point so I'm happy to help you I'm happy to help you parse the brain dump Nick, but if Michelle is available, she might be a better source.

E

I will not I will tackle it.

C

Okay and then the last thing is going through the new accumulator, which I've already begun to do and I just I, just kind of need for people to be available when I ask questions like this, they release notes. What's what is this? Is it still fixed I mean I I've been dropping questions in to slack. What is, where is the right place to drop those in to sink docks or to the individual? Sig's are sick release? Well, where do you want me to drop those well.

F

If you're asking about any of the ones that I dropped in there just doing sig release and tag me, okay,.

C

G

That's that's fine yeah.

A

That's three answer: okay,.

C

Cool so I think I think we'll be I. Think we'll be fine I'm about halfway through I'm about halfway through the known issue, accumulator and I. Think a lot of these known issues were already resolved, so I think will be so that's it. So that's that's where we are so I'm just kind of cranking along on this. So all I ask is when I pop up and say what's deal here. If people could answer me, then we'll be all set.

A

All right seems like a good idea: I'm.

C

Not worried how about that! That's.

A

Good as well so Michelle will be primary on the the storage stuff and then we'll just try and work through the others, as we can here in securities, um Caleb went in when Anna goes doing its thing, we're in the process. Does it actually read the release? Notes draft? Is that the very very end or that's.

D

Yes, that's like the very very end. Okay,.

A

Do we have any kind of way of warning about that or I mean what is the? What is the timing on that look like in case we're still kind of hacking in the docs, since.

D

It's in the cloud it, it won't prompt me to pause, so it imagine it'll run in our or so, but it's like sits in the cloud. It should be. It's it's fine, I'm, actually gonna file, a PR to move to nice to move to a larger machine type, so the cross builds should go faster, I'm not concerned about having to kick it off again. So if it's well, you know when get the signal. Erase notes are good I'll. Just kick it off again, assuming that it's not something that it'll miss.

D

This miss currently I'm, not yeah. Okay,.

A

Great awesome only somebody's working on putting the things in the notes, but for dependencies who's doing that.

A

What am I doing? No Tim, not DIMMs,.

C

Thank you, Tim.

D

Actually so hipster kook DNS and go over if you should. Actually, you should be able to grab that from the repository itself from today. So there's a basil file that will tell you the.

H

D

It built with, and you should be image bumps for kookiness and heap stir as well. So those should be nice and hard.

C

Okay, wait: where am I supposed to get this file.

D

In the root of the repository I believe there should be a I'll.

G

Try and put links to the things that I'm finding also, and maybe then we can distill this out into a how-to for next time.

B

A

All right so Jennifer anything for docs that needs to be sort of done. I mean I, mean.

E

No I mean Doc's typically are finalized after their release starts building yeah. At this point, I'm helping Nick on the persister volume bits of their release, notes I'm, having some interesting issues that are not unusual and some documentation will not make it in right away because I still getting 1.10 pr's. Today, oh boy.

B

E

You know that's just hey people I'm, just telling people flat out in the PRS what's going on, but at this point I got the help. I need and I don't have anything critical worst case. Things will shift first thing in the morning. We're gonna hit I, don't think we're gonna hit worst case. Okay, but just letting y'all know what.

A

All the production deployments that are going to get input in 110 right when this concept yeah searching for docs and oh my gosh, like.

A

E

Not, but you know we're down to the wire so I'm trying to be realistic about priorities.

A

Here indeed, yes, levity is important. Well, hey.

E

I, you know my local bash terminal just decided to throw all kinds of weird at me and my local me maker, wouldn't wasn't working and I learned all kinds of new things about so.

A

Everybody must bash alright, so release branch signal sin. You want to talk about all that good stuff and.

I

Yeah looks like you know, mostly fine, so I find to equate issues at fade yesterday. They were like hiding behind the GK evenness.

I

A

The TLDR in this place that we're not that they're not release plucking, and then we just need to be aware of them or yeah.

I

Six one six, forty Dom just updated a shoe, so it looks like a testing environment thing and it's the only so it should not be a uni stalker, its resource tracking for 100 pots per node.

I

I think this will need to be think they will still need to fix this thing. A patch release, but I mean it's only on.

H

I

So seeing signal this get a handle on this, the other one is the GTE done great test. Had a failure on should ensure that critical part is scheduling is scheduled in case there's no resources available, but after I look at the test code, the the test is depend on the dashboard cuneta dashboard pod, which is not started by default on GE anymore, on when pans, so that tests need to be attached.

I

And that should awesome obviate Bucer.

I

The last thing my open issue is oh no mine, but killed at the cube at mean, wouldn't I, know intend. Job is moved out of the my zone, so yeah, okay,.

A

Alright, so in terms of the blocking tests, everything still is green or known. What's going on the last time, I look they're still look like they were still suffering from a few things.

I

If you click through the red tabs, the toughie he trigger is like oh yeah, all set for like four consecutive greens. Now this good bitty one looks like a one time: Freight yeah.

A

That one's that's the one that's just been worked for for a while cool okay. Well then, we we have recorded on video the those who are green at the time here, and everybody sees that which is good.

A

A

Alright, so boy sure looks like this cake might be baked to me. Is there anything else that we're missing anybody see any risks concerns things that need to be addressed other than the things we talked about this far.

A

All right, well, it looks like we're. Gonna have a bouncing, maybe kubernetes today, assuming that the build process works and that the cloud delivers as it should for for Caleb. So so the next steps are Caleb. This is now officially your show. I am turning over the release to you, and you are. You are the the owner from here forward.

B

A

And then just a recap: 5 p.m. Pacific. We will do the official release, announcement and blog pronouncements, etc. I would love for everybody on the team to tweet as much as you feel comfortable doing so to help spread. The word about this release and I think that's pretty much it we're going to do. The Oh Josh is asking who's doing the dependency thing. Who is doing the dependency thing I just.

F

Hey I have a bunch of notes from recent merges: okay.

A

Who's on point: for that I'm happy to help, do it as well, if necessary,.

A

F

Responsible for it, okay, if somebody's say again see you in Sigma lease about that, then yeah.

C

Okay, adding them now fantastic. Thank you so.

A

Good, okay, so just to be absolutely clear on this. We're gonna discuss this in the channel and we're going to collab collaboratively I get these soft. So if you see one there and you know how to how to find the information through the basil build or whatever then grab it, otherwise, it'll be just a little bit of schlepping through the code base to find those.

A

Okay, good and Natasha I have a couple questions for the blog TAS go right ahead: yep.

H

So for the blog, everything is done and reviewed and looks great I just need someone to insert the link of where you can download it on github and the link for the interactive tutorial.

H

And then I just want to let you know that the blog for the blog series, following the release, is actually going to be a two day blog series. We were only able to get storage to assist with writing blogs as well as participating in the April 10th webinar, so I'm just doing a last call to everyone. If you would like to talk about, if you have a major feature and you'd like to talk about it outside storage, please play ping Kaitlyn Barnard today or forever hold your peace. We're just moving forward.

H

And then last step we have an email interview occurring with a week right now, I tagged several people in the email interview and just if you've been tagged in that over email, please just go in. If you can answer any of the questions that is due in an hour and a half for a story, and then anybody that read the tech target story on Friday I have been in contact with the reporter Thank You Nick, and your for helping you with the correction and in our release.

H

Recap: I'll, inform everybody what happened and then also give some advice on how we can avoid that in the future, and that's all for me.

A

Okay yeah, so if anybody's got a blog, if you're inspired to write a blog for this thing, yeah, it's just definitely show them the tush in and do that.

A

A

And Natasha you're gonna be able to make the retro right.

H

When is the retro Thursday.

A

It's 10:00 a.m. Pacific.

H

Yes, is it just the regular community meeting that we've streamed Island, or will this be a new okay? The.

A

Exact, listen, okay, great fantastic, because I think you'll have a lot of really valuable feedback there. Well.

H

That's that I want to be able to get feedback for I know maternity leave.

A

H

Have a lot for you good! Yes,.

A

That's awesome, okay, so any other things before we adjourn.

A

All right, this is my last opportunity to thank everybody again. I know, I keep thinking everybody effusive ly over and over again, but really this is is just such an amazing team. I feel so honored to be amongst such greatness, and thank you all again for three solid months of investment in this. This has not been a small or trivial thing to work on, so you all are the best and truly truly make this community exactly what it is, which is the best community.

A

So thank you all, truly, truly thankful and with that before I get all misty I'm going to call it and and say we will see you in the slack channel and.

A

Soon, we will have a release to share with the world, so thank you. Everybody.

D

Thank you, Jase Thank,.

G

You Joyce yeah truly.

A