- We do not recommend upgrading to Kubernetes 1.19.0 due to an upstream bug in kubeadm affecting Highly-Available clusters. The bug will be fixed in 1.19.1, which is scheduled for Wednesday, September 9th. Until 1.19.1 is not released, we highly recommend staying on 1.18.
- Include cloud-config in the generated KubeOne configuration manifest when it's required by validation (#1062)
- Properly apply labels when upgrading components. This fixes the issue with upgrade failures on clusters created with KubeOne v1.0.0-rc.0 and earlier (#1078)
- Fix race condition between kube-proxy and node-local-dns (#1058)
SHA256 checksums can be found in the