Provide binary for releases

[rvrignaud]

Hello,

It would be great if community could provide Linux/amd64 binaries for releases.

Thoughts ?

[brancz]

I am completely for this, however, it would have to be completely automated and as far as I understand this is part of the effort of opening up google's internal release process to non google maintainers.

/cc @saad-ali @grodrigues3 @piosz @david-mcmahon

[andyxning]

@rvrignaud I am not sure whether you want release binaries or release images.

As for release binaries, maybe #153 will fully accomplish your requirement with also supporting multi arches.

[brancz]

As mentioned in the PR, I don't think we will start releasing binaries, until google opens up the release process to us. For the time being it will just be amd64 container images that are published on gcr by google people and on quay by me or @fabxc.

[grodrigues3]

@kubernetes/sig-release-feature-requests

[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

[coffeepac]

@brancz is this the issue you were talking about during sig-inst today, re: opening the build process?

[brancz]

@coffeepac yes this, this and this. They all revolve around the same topic, essentially how can we as non-Googlers do releases independently.

[coffeepac]

/remove-lifecycle stale

[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.

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

[brancz]

/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