Automate and improve our release process

[chrislovecnm]

At this point, only one maintainer is able to create a release for kops. This is a risk that needs to be resolved. Risks include:

• single point of failure
• if we have a p0 bug only one person can release
• if the user wins the lottery we have no release avenue

The release includes both the primary ami that is used for kops, and kops itself. The primary ami is built using tooling out of https://github.com/kubernetes/kube-deploy/tree/master/imagebuilder

Also, the kernel for the ami is not mainstream, but a custom build.

Proposed Solutions

Interm

1. we need to document existing process
2. determine which shared file repository and container registry we can use for the release
3. We can automate a release process via Travis, but it seems kinda complicated.

Any other ideas

Long Term

We have multiple smaller projects within k8s now that will all need a process. We can possibly start with looking at what mini-kube and helm are using. I believe this should be under the purview of sig-release.

Really need ideas for this

[justinsb]

The release process is documented at https://github.com/kubernetes/kops/blob/master/docs/development/release.md

The github release itself can be done by anyone with the right github permissions, following those instructions. The kubernetes project can create additional repo administrators etc.

Anyone can upload the artifacts to their own location and change the default paths using https://github.com/kubernetes/kops/blob/master/docs/development/adding_a_feature.md#testing

We remain very open to a better place to host the artifacts. I believe the tool that is currently used for k8s releases is anago.

[chrislovecnm]

We now have a functioning build queue.

https://kops.submit-queue.k8s.io/#/queue

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[chrislovecnm]

/lifecycle frozen
/remove-lifecycle rotten