Kubeadm 1.5 Plan

[Saad Ali]

There was a discussion on slack (partial transcript below) about Kubeadm PRs and trying to get them merged in time for 1.5.

Apparently kubeadm's release is decoupled from the primary kubernetes release for 1.5.

I'd like to understand how/why this happened, what the current plan is for the kubeadm 1.5 release, and make sure there are no issues with having a decoupled release.

> briangrant [1:56 PM]  

> @luxas So long as you're in the kubernetes repo, you need to follow the same process and policies as everything else in the kubernetes repo

> 

> [1:57]  

> I assume that kubeadm will be in the 1.5 kubernetes release bundle

> ...

> [1:58]  

> If kubeadm is in the kubernetes release bundle, then it is versioned together with everything else in the bundle.

> 

> luxas [1:59 PM]  

> Yes, that's the "second" stable release of kubeadm (while still in alpha), but the "third" (which I'm trying to get together now) will include v1.5 support

> 

> [2:00]  

> And will be released from the main repo ~when v1.5 is released

> 

> briangrant [2:00 PM]  

> @luxas Release 1.5.0 of kubeadm must come from the same branch and tag as 1.5.0 of Kubernetes

> 

> luxas [2:00 PM]  

> But for v1.6, we intend to sync the process up, but we didn't want to bother the v1.5 release process yet

> 

> [2:01]  

> It won't be tagged 1.5.0, it just will be released at the same time from master to the deb/rpm-repos

> 

> briangrant [2:04 PM]  

> @luxas That sounds pretty broken to me, but we should move this discussion to somewhere more durable, like the mailing list or a github issue

> 

> luxas [2:06]  

> My plan at least is to split kubeadm out, vendor in a stable version of it to v1.6 and have the "real", stable kubeadm v1.6 binary in the v1.6 tarball

> ...

> [2:09]  

> There wasn't just enough time in v1.5 to get it right... As I said earlier, I would have preferred that kubeadm if kubeadm never got merged into the main repo but another kubernetes/ repo directly, but the folks didn't agree with me at the time (probably too little time there as well)

> 

> [2:11]  

> @saad-ali @briangrant But if I'm allowed to set the v1.5 on kubeadm PRs which won't disturb the v1.5 that much on kubeadm PRs, I'll do it tomorrow

> 

> briangrant [2:12 PM]  

> @luxas What kinds of changes are being made to kubeadm? We're in feature freeze and bug-fix mode.

> 

> luxas [2:12 PM]  

> Stabilization and UX improvements mostly

> 

> briangrant [2:12 PM]  

> Also, anything that needs to be in the release-1.5 branch needs to be cherrypicked at this point

> 

> [2:13]  

> And we'd like that to not be hundreds of PRs

> 

> luxas [2:13 PM]  

> Nothing would get into the release-1.5 branch

> 

> [2:13]  

> Only master

> 

> briangrant [2:13 PM]  

> Then you need to wait for the freeze to lift

> 

> luxas [2:13 PM]  

> (Since we're not using the release branch yet)

> 

> [2:13]  

> What do you mean? The code freeze lifted today right?

> 

> briangrant [2:14 PM]  

> Then you shouldn't need any special labels or milestones

> 

> luxas [2:16 PM]  

> Ok, I'll wait some days and see how fast the process is then (the intension was never to block v1.5 prs, but to get the kubeadm prs quickly away from the queue if possible)

[Saad Ali]

Ping. Is it worth having a discussion about kubeadm 1.5 release plan?

[Mike Danese]

Hi Saad,

We discussed this in our sig meeting this morning and have removed
priorities from all kubeadm PRs. We are comfortable with the release
being cut as is.

Kubeadm is alpha in v1.5 and for as long as it remains alpha we are
planning on pushing approximately monthly releases cut from master to
the deb/rpm repos. This is what we've done in the past. Once we bring
kubeadm to beta, we will tie into the main release process but until
that happens we want to deliver fixes and features to alpha users to
get feedback. I'm happy to have a detailed conversation on what was
discussed if you would like.

TLDR: Please don't let us slow you down.

Thanks!
Mike Danese

On Tue, Nov 29, 2016 at 1:59 PM, 'Saad Ali' via
kubernetes-sig-cluster-lifecycle

> --
> You received this message because you are subscribed to the Google Groups
> "kubernetes-sig-cluster-lifecycle" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to kubernetes-sig-cluster...@googlegroups.com.
> To post to this group, send email to
> kubernetes-sig-c...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/kubernetes-sig-cluster-lifecycle/b8136679-0fcc-4ee2-8237-3dc2cf833773%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.

[Saad Ali]

Thanks for the summary Mike! Sounds good. I'll ignore kubeadm for the purposes of the 1.5 release then.

On Tue, Nov 29, 2016 at 2:34 PM, 'Mike Danese' via kubernetes-sig-cluster-lifecycle <kubernetes-sig-c...@googlegroups.com> wrote:

Hi Saad,

We discussed this in our sig meeting this morning and have removed
priorities from all kubeadm PRs. We are comfortable with the release
being cut as is.

Kubeadm is alpha in v1.5 and for as long as it remains alpha we are
planning on pushing approximately monthly releases cut from master to
the deb/rpm repos. This is what we've done in the past. Once we bring
kubeadm to beta, we will tie into the main release process but until
that happens we want to deliver fixes and features to alpha users to
get feedback. I'm happy to have a detailed conversation on what was
discussed if you would like.

TLDR: Please don't let us slow you down.

Thanks!
Mike Danese

On Tue, Nov 29, 2016 at 1:59 PM, 'Saad Ali' via
kubernetes-sig-cluster-lifecycle

> email to kubernetes-sig-cluster-lifecycle+unsubscribe@googlegroups.com.

> To post to this group, send email to

> kubernetes-sig-cluster-life...@googlegroups.com.

> To view this discussion on the web visit
> https://groups.google.com/d/msgid/kubernetes-sig-cluster-lifecycle/b8136679-0fcc-4ee2-8237-3dc2cf833773%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "kubernetes-sig-cluster-lifecycle" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/kubernetes-sig-cluster-lifecycle/P2oh5iHWBsA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to kubernetes-sig-cluster-lifecycle+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-sig-cluster-life...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-cluster-lifecycle/CAMu1AU57_iEckifC_DWA1kft2mdphGkexPyF6edn1RxUsj1-_A%40mail.gmail.com.