KubeOne v1.3.0
Today, we are pleased to announce that KubeOne 1.3 is now generally available. The previous release paved a road for many new features and this time we are excited to present those features to you. KubeOne 1.3 brings a brand new Addons API, managed support for encryption providers, automated Docker to containerd migration, and more!
Major Highlights
We recommend checking out the Upgrading from KubeOne 1.2 to 1.3 tutorial, as well as, the changelog for more information about upgrading and the latest features and improvements.
Attention Needed
Breaking changes / Action Required
- Increase the minimum Kubernetes version to v1.19.0. If you have Kubernetes clusters running v1.18 or older, you need to use an older KubeOne release to upgrade them to v1.19, and then upgrade to KubeOne 1.3.
- Increase the minimum Terraform version to 1.0.0.
- Remove support for Debian and RHEL 7 clusters. If you have Debian clusters, we recommend migrating to another operating system, for example Ubuntu. If you have RHEL 7 clusters, you should consider migrating to RHEL 8 which is supported.
- Automatically deploy CSI plugins for Hetzner, OpenStack, and vSphere clusters using external cloud provider. If you already have the CSI plugin deployed, you need to make sure that your CSI plugin deployment is compatible with the KubeOne CSI plugin addon.
- The
kubeone resetcommand requires an explicit confirmation like theapplycommand starting with this release. The command can be automatically approved by using the--auto-approveflag.
Deprecations
- KubeOne Addons can now be organized into subdirectories. It currently remains possible to put addons in the root of the addons directory, however, this is option is considered as deprecated as of this release. We highly recommend all users to reorganize their addons into subdirectories, where each subdirectory is for YAML manifests related to one addon.
- We're deprecating support for CentOS 8 because it's reaching End-of-Life (EOL) on December 31, 2021. CentOS 7 remains supported by KubeOne for now.
Checksums
SHA256 checksums can be found in the kubeone_1.3.0_checksums.txt file.