The KubeOne documentation has been migrated from GitHub to the new KubeOne docs website. Checkout the new website to find out how to get started with KubeOne.
Attention Needed
- It's recommended to use this release instead of v0.11, as v0.11 doesn't support the latest Kubernetes patch releases. Older Kubernetes releases are affected by two CVEs and therefore it's strongly advised to use 1.16.11/1.17.7/1.18.4 or newer.
Known Issues
- machine-controller is failing to sign Kubelet CertificateSingingRequests (CSRs) for worker nodes on GCP due to missing hostname in the Machine object. We are currently working on a fix. In meanwhile, you can sign the CSRs manually by following instructions from the Kubernetes docs.
- It remains impossible to provision Kubernetes 1.16.10+ clusters on CentOS 7. CentOS 8 and RHEL are unaffected. We are investigating the root cause of the issue.
- Trying to upgrade cluster created with KubeOne v0.11.2 or older results in an error due to KubeOne failing to upgrade the
docker-ce-clipackage. This issue has been fixed in the v1.0.0-beta.1 release.
Changed
General
- Re-introduce the support for the kubernetes-cni package and use the proper revision for Kubernetes packages (#933)
- This change ensures operators can use KubeOne to install the latest Kubernetes releases on CentOS/RHEL
Bug Fixes
- Stop copying kubeconfig to the home directory on control plane instances (#936)
- This fixes the issue with upgrading CoreOS/Flatcar clusters
Updated
- Update machine-controller to v1.14.3 (#937)
Checksums
SHA256 checksums can be found in the kubeone_1.0.0-beta.0_checksums.txt file.