Removing arch-specific binaries from kubernetes.tar.gz "full" tarball

38 views
Skip to first unread message

Jeff Grafton

unread,
Oct 27, 2016, 7:21:54 PM10/27/16
to kubernetes-dev
As part of the effort to make the size of our release tarballs more manageable, I am removing the arch-specific client and server binaries from the kubernetes.tar.gz tarball, starting with the 1.5 release. Pull request is here. More details of this effort are described in this issue (and linked issues).

The client and server tarballs will continue to be available as arch-specific downloads in the GCS release bucket.

To facilitate this change:
  • All references to kubernetes.tar.gz in the kubernetes/kubernetes repo have been updated to explicitly use the server or client tarballs instead.
  • The tooling used by https://get.k8s.io/ has been updated to automatically download necessary client and server binaries (via the cluster/get-kube-binaries.sh script).
  • CI testing has been updated to use the https://get.k8s.io/ workflow.
  • The CHANGELOG now links to all arch-specific downloads (example).
As this may cause issues downstream outside our control, I advise testing the 1.5 beta releases as soon as they are available.

Please let me know (or comment on the PR) if you expect this change to significantly break your workflow.

Thanks!

Klaus Ma

unread,
Oct 27, 2016, 10:12:15 PM10/27/16
to Kubernetes developer/contributor discussion
+1

BTW, does it make sense to provide a client package which only include kubectl?

Thank
Klaus

Jeff Grafton

unread,
Oct 28, 2016, 1:14:18 AM10/28/16
to Klaus Ma, Kubernetes developer/contributor discussion
Possibly not. I'm not sure if we ever expect to ship anything besides kubectl in the client archives.

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-dev@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/97ee88c6-1093-4203-b7a1-ab5b0c251756%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Clayton Coleman

unread,
Oct 28, 2016, 9:58:30 AM10/28/16
to Jeff Grafton, Klaus Ma, Kubernetes developer/contributor discussion
kubeadm?  kubefed?
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-de...@googlegroups.com.
To post to this group, send email to kuberne...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/CA%2B8-4Sm_xYgvszXrVKDbw5vi%3DSJ%3DuMtADGjEdBmttSOcL6Dhdg%40mail.gmail.com.

Brian Grant

unread,
Oct 28, 2016, 10:09:50 AM10/28/16
to Clayton Coleman, Jeff Grafton, Klaus Ma, Kubernetes developer/contributor discussion
On Fri, Oct 28, 2016 at 6:58 AM, Clayton Coleman <ccol...@redhat.com> wrote:
kubeadm?  kubefed?

On Oct 28, 2016, at 1:14 AM, 'Jeff Grafton' via Kubernetes developer/contributor discussion <kubernetes-dev@googlegroups.com> wrote:

Possibly not. I'm not sure if we ever expect to ship anything besides kubectl in the client archives.
On Thu, Oct 27, 2016 at 7:12 PM, Klaus Ma <klaus1...@gmail.com> wrote:
+1

BTW, does it make sense to provide a client package which only include kubectl?

Thank
Klaus


On Friday, October 28, 2016 at 7:21:54 AM UTC+8, Jeff Grafton wrote:
As part of the effort to make the size of our release tarballs more manageable, I am removing the arch-specific client and server binaries from the kubernetes.tar.gz tarball, starting with the 1.5 release. Pull request is here. More details of this effort are described in this issue (and linked issues).

The client and server tarballs will continue to be available as arch-specific downloads in the GCS release bucket.

To facilitate this change:
  • All references to kubernetes.tar.gz in the kubernetes/kubernetes repo have been updated to explicitly use the server or client tarballs instead.
  • The tooling used by https://get.k8s.io/ has been updated to automatically download necessary client and server binaries (via the cluster/get-kube-binaries.sh script).
  • CI testing has been updated to use the https://get.k8s.io/ workflow.
  • The CHANGELOG now links to all arch-specific downloads (example).
As this may cause issues downstream outside our control, I advise testing the 1.5 beta releases as soon as they are available.

Please let me know (or comment on the PR) if you expect this change to significantly break your workflow.

Thanks!

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com.
To post to this group, send email to kuberne...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-dev@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-dev@googlegroups.com.

Brian Grant

unread,
Oct 28, 2016, 10:12:53 AM10/28/16
to Clayton Coleman, Jeff Grafton, Klaus Ma, Kubernetes developer/contributor discussion

kubeadm?  kubefed?

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com.
To post to this group, send email to kuberne...@googlegroups.com.
Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages