v0.4.0 brings improved networking features in particular, including initial IPv6 support and additional node port forwards. It also continues to improve speed and reliability (hopefully!
- The default node image is a Kubernetes v1.15.0 image
- The deprecated
kind.sigs.k8s.io/v1alpha2version of config was removed, please switch to
kind build node-image --type=aptwas removed. Please use
kind build node-imageor
kind build node-image --type=bazelinstead, or one of the pre-built images. A future release will re-work these commands and add support for building from upstream release tarballs.
- Additional node port forwards may be configured with the
kind.sigs.k8s.io/v1alpha3. This can be used to access workloads more easily from the host. Expect guides using this soon!
- Limited IPv6 support. The
networking.ipFamilymay be set to
Clusterconfiguration to create an ipv6 enabled cluster on Linux. We have set up continuous Kubernetes conformance testing with IPv6 enabled and are working to fix the tests
- A warning is emitted if the chosen cluster name is too long and likely to cause the generated node names to be too long.
make installnow supports overriding
INSTALLto specify an alternate tool to
installand ensures the output directory
- Support / documentation for using kind on WSL2.
kind load ...sub-commands now avoid loading images that are already present
v1beta2config is now use opportunistically for recent enough Kubernetes versions
- Reduced startup time for single-node clusters in particular
New Node have been Images for kind
v0.4.0, please use these exact images or build your own as we may need to change the image format again in the future
- The generated KUBECONFIG file references the API Server by listen address (IP) instead of
localhost(domain), which is more correct and should work on systems without a valid
- The new kind images should work on ipv4 only hosts with ipv6 fully disabled
- The node subnet is properly added included in
NO_PROXYon the nodes when proxy settings are detected
- Clusters with multiple control plane nodes now have proper healthchecks of the API servers in the external loadbalancer
- Minor cleanup and typo fixes
Thanks again to everyone who committed to this release! You all are the best!
Alphabetically by user name: