UPDATE 2019-02-11

Due to CVE-2019-5736 ("the runc escape")

kindest/node:v1.12.5@sha256:2cc6e8153dbe32db0b962cda060e193615951ae8d2a0b808535726a9b6b5e583 or kindest/node:v1.13.2@sha256:d070e091e7c0e515a37d0834ea72828b2338acdc4bc7a13cbb84274fb14e5e83 or: kindest/node:v1.13.3@sha256:d1af504f20f3450ccb7aed63b67ec61c156f9ed3e8b0d973b3dee3c95991753c

Should be used instead of the default image in this release. Example:

kind create cluster --image=kindest/node:v1.13.3@sha256:d1af504f20f3450ccb7aed63b67ec61c156f9ed3e8b0d973b3dee3c95991753c

In the future we are looking at not pinning to an exact image by default, so that minimal fixes can be silently pushed. We are additionally hoping to adopt rootless containers once support lands in Kubernetes.

Please consider upgrading to kind 0.1.0 or newer as well.

UPDATE: Kubernetes v1.12.2 is affected by CVE-2018-1002105; when using kind create cluster please set the image to a non-default image via the --image flag. The following Kubernetes v1.12.3 image should be suitable: kindest/node:v1.12.3@sha256:f0ecb1066697d9417365ca58410132e512ce2010763470bb28c1e8f7fef55464

A patch release will be made to upgrade this default, see https://github.com/kubernetes-sigs/kind/issues/180.

kind is still alpha-grade software, and as such breaking changes will be made to future releases.

This release allows early users to pin to these pre-built binaries and avoid these changes until they intend to upgrade, rather than installing from HEAD with go get ...

NOTE: the default kind create cluster pins to a specific node image in order to avoid breakage there.

This image is: kindest/node:v1.12.2@sha256:6ac1dc1750fc0efd13d4e294115f9012a21282957e4380a5535bd32154193d4d on the current official registry.

Contributors to this release are:

• @BenTheElder
• @munnerz
• @alejandrox1
• @tao12345666333
• @neolit123
• @fabriziopandini
• @Lion-Wei
• @mooncak
• @radu-matei
• @AdamDang
• @cblecker

Thank you for your contributions!