-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide binary for releases #85
Comments
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. |
@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. |
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. |
@kubernetes/sig-release-feature-requests |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
@brancz is this the issue you were talking about during sig-inst today, re: opening the build process? |
@coffeepac yes this, this and this. They all revolve around the same topic, essentially how can we as non-Googlers do releases independently. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
…ry-pick-84-to-release-4.11 [release-4.11] OCPBUGS-4087: cherry-pick, do not expose ingress path metric when service is nil
Hello,
It would be great if community could provide Linux/amd64 binaries for releases.
Thoughts ?
The text was updated successfully, but these errors were encountered: