Releases: kubermatic/kubeone
v0.7.0
Check out the documentation for this release to find out how to get started with KubeOne.
Make sure to check the release notes for v0.6.0 if you're upgrading from v0.5.0 or earlier.
Added
- Add WeaveNet as an additional CNI plugin (#432)
- Add the
--remove-binaries
flag to thekubeone reset
command that removes Kubernetes binaries (#450)
Changed
- Fix
kubeone reset
failing if noMachineDeployment
orMachine
object exist (#450) - Update
machine-controller
to v1.1.8 (#454)
Checksums
SHA256 checksums can be found in the kubeone_0.7.0_checksums.txt
file.
v0.6.2
Check out the documentation for this release to find out how to get started with KubeOne.
Make sure to check the release notes for v0.6.0 if you're upgrading from v0.5.0 or earlier.
Changed
- Fix a missing JSON tag on the
Name
field, so specifyingname
in lowercase in the manifest works as expected (#439) - Fix failing to disable SELinux on CentOS if it's already disabled (#443)
- Fix setting permissions on the remote KubeOne directory when the
$USER
environment variable isn't set (#443)
Checksums
SHA256 checksums can be found in the kubeone_0.6.2_checksums.txt
file.
v0.6.1
Check out the documentation for this release to find out how to get started with KubeOne.
Make sure to check the release notes for v0.6.0 if you're upgrading from v0.5.0 or earlier.
Changed
- Provide the
--kubelet-preferred-address-types
flag to metrics-server, so it works on all providers (#424)
Checksums
SHA256 checksums can be found in the kubeone_0.6.1_checksums.txt
file.
v0.6.0
We're excited to announce that as of this release KubeOne is in beta! We have the new backwards compatibility policy going in effect as of this release.
Check out the documentation for this release to find out how to get started with KubeOne.
Action Required
- This release introduces the new KubeOneCluster API. The new API is supposed to improve the user experience and bring many new possibilities, like API versioning.
- Old KubeOne configuration manifests will not work as of this release!
- To continue using KubeOne, you need to migrate your existing manifests to the new KubeOneCluster API. Follow the migration guidelines to find out how to migrate.
Added
- [BREAKING] Implement and migrate to the KubeOneCluster API (#343, #353, #360, #379, #390)
- Implement the
config migrate
command for migrating old configuration manifests to KubeOneCluster manifests (#408) - Implement the
config print
command for printing an example KubeOneCluster manifest (#412, #415) - Enable scaling subresource for MachineDeployments (#334)
- Deploy
metrics-server
by default (#338, #351) - Deploy external cloud controller manager for DigitalOcean, Hetzner, and Packet (#364)
- Implement Terraform integration for Hetzner (#331)
- Add support for OpenIDConnect configuration (#344)
- Add support for Packet provider (#384)
- Patch CoreDNS deployment to work with external cloud controller manager taints (#362)
Changed
- Fix a typo in vSphere CloudProviderName (#339)
- Expose
ssh_username
variable in the Terraform output (#350) - Pass
-external-cloud-provider
flag tomachine-controller
when external cloud provider is enabled (#361) - Update
machine-controller
to v1.1.5 (#378) - Don't wait for
machine-controller
if it's not deployed (#392) - Deploy instance with a load balancer on OpenStack. General improvements to OpenStack support (#401)
- Parse all parameters from Terraform output for DigitalOcean (#370)
Checksums
SHA256 checksums can be found in the kubeone_0.6.0_checksums.txt
file.
v0.5.0
Check out the documentation for this release to find out how to get started with KubeOne.
Added
- Add support for Kubernetes 1.14
- Add support for upgrading from Kubernetes 1.13 to 1.14
- Add support for Google Compute Engine (#307, #317)
- Update machine-controller when upgrading the cluster (#304)
- Add timeout after upgrading each node to let nodes to settle down (#316, #319)
Changed
- Deploy machine-controller v1.1.2 on the new clusters (#317)
- Creating MachineDeployments and upgrading nodes tasks are repeated three times on the failure (#328)
- Allow upgrading to the same Kubernetes version (#315)
- Allow the custom VPC to be used with the example AWS Terraform scripts and switch to the T3 instances (#306)
Checksums
Checksums can be found in the kubeone_0.5.0_checksums.txt
file.
v0.4.1
Action Needed
- Due to breaking changes in the Kubernetes package dependencies in order to be able to create and upgrade clusters you need to upgrade KubeOne to the version 0.4.1.
Changed
- Bind the
kubernetes-cni
package to 0.7.5 for 1.13.5+ clusters and to 0.6.0 for the older clusters (#309)
Checksums
Checksums can be found in the kubeone_0.4.1_checksums.txt
file.
v0.4.0
Action Needed
- In #264 the environment variable names were changed to match names used by Terraform. In order for KubeOne to correctly fetch credentials you need to use the following variables:
DIGITALOCEAN_TOKEN
instead ofDO_TOKEN
OS_USERNAME
instead ofOS_USER_NAME
HCLOUD_TOKEN
instead ofHZ_TOKEN
- The
cloud-config
file is now required for OpenStack clusters. Validation will fail if thecloud-config
is not provided. See the OpenStack quickstart for details how thecloud-config
file should look like. - Ark integration is removed from KubeOne in #265. You need to remove the
backups
section from the existing configuration files. If you wish to deploy Ark on new clusters you have to do it manually.
Added
- Add support for enabling DynamicAuditing (#261)
Changed
- Deploy machine-controller v1.0.7 on the new clusters (#247)
- Automatically download the Kubeconfing file after install (#248)
- Default
--destory-workers
totrue
for thekubeone reset
command (#252) - Improve OpenStack Terraform scripts (#253)
- The
cloud-config
file for OpenStack is required (#253) - The environment variable names are changed to match names used by Terraform (#264)
Removed
- Option for deploying Ark is removed (#265)
Checksums
Checksums can be found in the kubeone_0.4.0_checksums.txt
file.
v0.3.0
Action Needed
- If you're using
provider.Name
external
to configure control plane nodes to work with external CCM you need to:- Set
provider.Name
to name of the cloud provider you're using or tonone
(seeconfig.yaml.dist
for supported values), - Set
provider.External
totrue
. - Note: using external CCM is not supported and is currently not working as expected.
- Set
- If you're using
provider.Name
none
:- If you're deploying
machine-controller
you need to setMachineController.Provider
to name of the cloud provider you're using for worker nodes, - Otherwise you need to set
MachineController.Deploy
tofalse
, so validation passes.
- If you're deploying
Added
- Add support for cluster upgrades (#206, #211, #214)
- Add support for enabling PodSecurityPolicy (#218)
- Add
kubeone version
command (#221) - Add initial support for OpenStack worker nodes (#209)
Changed
- Fix
none
provider bugs and ensure correct behavior (#227) - External Cloud Controller Manager is now enabled by setting
Provider.External
totrue
instead of settingProvider.Name
toexternal
(#230, #237) - Set correct Internal address on nodes with 2+ network interfaces (#240)
- Deploy
machine-controller
on uninitialized nodes (#241)
Checksums
Checksums can be found in the kubeone_0.3.0_checksums.txt
file.
v0.3.0-beta1
Add Provider.EnableCCM API field (#230)
v0.2.0
Added
- Add support for workers creation on DigitalOcean (#153)
- Add support for CentOS (#154)
- Add support for external cloud controller managers (#161)
- Add Terraform scripts for OpenStack (#170)
- Add support for configuring proxy for Docker daemon,
apt-get
/yum
andcurl
(#182)
Changed
- AWS credentials can be obtained from the profile file (#156)
- Fix Etcd init on clusters with more than one network interface (#160)
- Allow
provider.Name
to be specified for providers without external Cloud Controller Manager (#161) - Refactor KubeOne CLI (#177)
- Global flags are parsed correctly regardless of their placement in the command
--verbose
and--tfjson
are global flags- The main package is moved to the root of project (
github.com/kubermatic/kubeone
)
- Deploy
machine-controller
v1.0.4 instead of v0.10.0 to fix CVE-2019-5736 (#191) - Deploy Docker 18.09.2 on Ubuntu to fix CVE-2019-5736 (#193)
Removed
Checksums
4e7041db290f74710147ad7862afc84b41a4ab18a0a9684d51efdb34891e1f29 kubeone_v0.2.0_linux_amd64.tar.gz