Kubernetes SIG Release, 17 Jun 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: How-To: Cutting a Kubernetes Release

Description

This is a walk-through for the Branch Management role on the Release Team for how to cut a new release from start to finish.

For more info, please visit

github.com/kubernetes/sig-release/tree/master/release-team/role-handbooks/branch-manager

A

Hello in this video I'll be showing the process of cutting release candidate. One for version 1.15 today happens to be release day, which is June 11th and on my browser, I have the branch manager handbook open on section RC build I'll, be going through each of the items listed in detail so first things.

A

First, when cutting a release is the opening issue, and here I have are someone release cut, opened on single easy so going through the checklist I've made for myself I'm using the pre or using the issue template so item 1, which is make sure that OPR is in milestone? V 1.15 are all merge. This happens to be the first item listed in this section, so I have that open right here.

A

So, as you can see that all PRS under Musto 1.15 are not open. They're all closed, so I can go ahead and check that off. So the next thing to do is branch past 4th prior to cutting RC 1, which is mentioned in item 2 of this section.

A

So I went ahead and done that- and this is this- is the output of the branch past board done earlier, which took about 8 minutes, and you can see the changes pushed on to release 1.15 the 115 branch. So it happens to be these two important PRS that were merged, so I can go ahead and check this one on. So the next item is to make sure that there are no blocking PRS.

A

In this case we want to talk to the release team and, while by attending the release or talking to the least lead in this case, PR, seven eight eight eight triple eight five was a blocking PR. So in order to go ahead with this release, I had to make sure that this PR was merged.

A

Before going ahead with the release process, so in this case it has been merged, so I can go ahead and check that one off, and this is wrong. So I've done this I've done item one two. So we'll move on to item three.

A

Which I did not mention on this checklist, so going into detail about or just long story short about what this is talking about, so usually the release. After cutting the list release candidate, one code, thaw happens or in other words we lift code freeze. So when do we do that when is code freeze lifted? So there are several things to keep in mind.

A

First of all, there are no open PRS marked with master one, which we've seen earlier, which we've seen here and then next thing to consider would be to make sure that on no failing, 1.15 watching tennis so bring that up which happens to be this one. So in this case it looks pretty green, so wool flaky test, but, as you can see, cygnus 1.15 all is not doing too good.

A

This consideration, and also the consideration of CI signal and release need that whether or not cold fish cold freeze should be lifted. So, oh, and also there shouldn't be any issues marked with mouse, know, 1.15 to be addressed. Otherwise, there'll be a PR to address it to address it, and that means that you know we can't go forward with lifting the coal freeze. So having talked about I just want to in 3, we can go ahead and start the release process.

A

So I have my handy spreadsheet right here, so the command to do is not this. This was from the prior release that I copied over so I've copied over to my terminal. All I need to do is change this to 1.15 to the 1.15 branch, so I am staging the release branch in preparation for the release candidate here I'm, giving the flag release candidate and I want to build that head at the head.

A

Work I want to build from the green, build as indicated on test really, so you could also find that command right here as an example. So this was used in 1.12, so I'll go ahead and then execute this command.

A

It'll take a while and ignore these symbols, they're they're Unicode for the equal sign. So for some reason it's just not rendering. So we can go ahead and look at the output, oops I forgot to add dot. Smush.

A

So this will show the output from the console on google cloud.

A

So right now the status is in progress and we should get all green builds when you come back.

A

Welcome back but 50 minutes have passed as you can see. Google Cloud Builder manager has completed the skating process which took about 48 minutes and 10 seconds. We can also see that on the cloud hold the field steps have passed, which indicates a successful staging process, so next step would be to run the actual release.

A

The handy dandy commands get them right. There.

A

I'm gonna go ahead and execute the release process. This is not a dry run and it's for the least candidate one using the 1.15 French go ahead and do that and I would do my yes on that and the sings before we could see the progress flag then, as well as running TCP, MGR yeah.

A

So that shows in progress and will return who wants all these build steps are green.

A

Hello welcome back again right now the release cut for release candidate 180, as you can see here, it says done and it took about 17 minutes or so. You could also see that on the Google Cloud console right here and all the gold steps have passed. You could also verify this by going to crouppen any news releases and they go. You can see the least candidate one right there. So while that was building, I went ahead and took screenshots for dashboards.

A

That I thought were that would give the nice snapshot to what happened or to what was happening with tests. When really candidate one was being cut oops. That's not not! Everyone I.

A

Wanted to click on the drop down, so it looks like sig release. 1.15 all is experiencing the number of tests.

A

That's concerning part, the actual official release, but in this case for release candidate one it's doing. Okay, especially it was master, sig, release, master, informing and as well as Cygnus master, blocking, in fact, the one dashboard that we are most particularly interested in the moment. The sig release, 1.15 blocking routes, seems to be mostly green and couple of flakes, but overall it looks, doesn't look too concerning.

A

So now that we are done with the staging and movies process of Lily's candidate, one thank you go ahead and check that off and this one as well make a comment.

A

The next few steps would be sending out an email notification, notifying the slack channel and as well as collecting oh I've, already done them. We have collected metrics, which I've done over here. All I need to do is add the end time.

A

Not exactly accurate, but about put around go around 17 minutes, so I can go ahead and copy all of this and paste it onto.

A

This is just wonderful pasting from Google sheets onto a comment on. Github is a breeze, so, as you notice I've not done the mock phase for stage and release.

A

As you go towards the actual release cut you you wouldn't want to do, the mock dry runs for each stage and release, but in the case of beta 2 I did not. I did not go ahead and do that. If there was a case, I would have debug and contact the release team about it, but for beta 1, 0 and and others three elf, oh I've done a mock version of stage and release. I think that is a comment.

A

Okay, so next thing to do would be to get the content of that email notification and, since I have not done in the mock stage. First, the moth process for staging release. The content would be found on a different Google.

A

A

There you know.

A

We're looking for kubernetes release and it doesn't seem like it's showing on the console, so I'll go ahead. Yes, that URL just change this right here.

A

Go to archive, we should be able to find the 1.15. Oh.

A

Yes, yes, I'll just do this.

A

Strange that it's not working like that, but you know it's not too hard to find just scroll down and there we go.

A

There's the content for the announcement and the announcement title can be found in this folder under release companies under the release under the bucket called kubernetes release, which is located under the kubernetes release, project test project, kubernetes, release, test pony.

A

During that short pause, I went ahead and informed disagree, slack Channel about rc1 being released that you could see on kubernetes slash, given a is races and I gave a link to the notification underneath this text and then I also went ahead and sent out the email, so I was showing earlier the contents of the kubernetes real reasons bucket which contain the archives made by an ago. So these are the continent that I use to send out the email which can be shown on kubernetes announced.

A

So that's pretty much it with cutting release candidate. One hope you enjoyed this video.