From dfdfd964e31eb1020f64120ecb6f9847556cd0f3 Mon Sep 17 00:00:00 2001 From: "Krishnakumar R(KK)" <29471693+kkmsft@users.noreply.github.com> Date: Tue, 12 Nov 2019 08:01:46 -0800 Subject: [PATCH] Quick steps for generating hyperkube image --- cluster/images/hyperkube/README.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/cluster/images/hyperkube/README.md b/cluster/images/hyperkube/README.md index 2cd8c049ee9..09bcc762290 100644 --- a/cluster/images/hyperkube/README.md +++ b/cluster/images/hyperkube/README.md @@ -4,6 +4,20 @@ `hyperkube` is built for multiple architectures and _the image is pushed automatically on every release._ +#### Images for development scenarios + +During the development process, it's effective to just build only the required binaries for specific +architecture and generate single hyperkube image from it. The following shows how to generate +linux/amd64 hyperkube image: + +```console +# Run the following from the top level kubernetes directory, to build the binaries necessary for creating hyperkube image. +$ KUBE_BUILD_PLATFORMS=linux/amd64 make kube-apiserver kube-controller-manager kube-proxy kube-scheduler kubectl kubelet + +# Create and push the hyperkube image +$ REGISTRY= VERSION= ARCH=amd64 make -C cluster/images/hyperkube push +``` + #### How to release by hand ```console