Skip to content

v1.5.0-beta.0

Pre-release
Pre-release
Compare
Choose a tag to compare
@kubermatic-bot kubermatic-bot released this 04 Aug 14:17
v1.5.0-beta.0
This tag was signed with the committer’s verified signature.
xmudrii Marko Mudrinić
GPG key ID: F15730C52ACE0E9D
Learn about vigilant mode.
3800c3d
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Changelog

The complete changelog since the v1.4.0 release is available in CHANGELOG/CHANGELOG-1.5.md.

Urgent Upgrade Notes

  • Automatically apply the node-role.kubernetes.io/control-plane taint to nodes running Kubernetes 1.24. The taint is also applied when upgrading nodes from Kubernetes 1.23 to 1.24. You might need to adjust your workloads to tolerate the node-role.kubernetes.io/control-plane taint (in addition to the node-role.kubernetes.io/master taint). Workloads deployed by KubeOne will be adjusted automatically. (#2019, @xmudrii)
  • Kubeadm is now applying the node-role.kubernetes.io/control-plane label for Kubernetes 1.24 nodes. The old label (node-role.kubernetes.io/master) will be removed when upgrading the cluster to Kubernetes 1.24. All addons are updated to use the node-role.kubernetes.io/control-plane label selector instead. All addons now have toleration for node-role.kubernetes.io/control-plane taint in addition to toleration for node-role.kubernetes.io/master taint. If you are overriding addons, make sure to apply those changes before upgrading to Kubernetes 1.24. (#2017, @xmudrii)
  • Operating System Manager is enabled by default and is responsible for generating and managing user-data used for provisioning worker nodes
    • Existing worker machines will not be migrated to use OSM automatically. The user needs to manually rollout all MachineDeployments to start using OSM. This can be done by following the steps described in Rolling Restart MachineDeploments document
    • The user can opt-out from OSM by setting .operatingSystemManager.deploy to false in their KubeOneCluster manifest. (#2157, @ahmedwaleedmalik)
  • workers_replicas variable has been renamed to initial_machinedeployment_replicas in example Terraform configs for Hetzner (#2115, @adeniyistephen)
  • Change default instance size in example Terraform configs for Equinix Metal to c3.small.x86 because t1.small.x86 is not available any longer. If you're using the latest Terraform configs for Equinix Metal with an existing cluster, make sure to explicitly set the instance size (device_type and lb_device_type) in terraform.tfvars or otherwise your instances might get recreated (#2054, @xmudrii)
  • Update secret name for backup-restic addon to kubeone-backups-credentials. Manual migration steps are needed for users running KKP on top of a KubeOne installation and using both backup-restic addon from KubeOne and s3-exporter from KKP. Ensure that the s3-credentials Secret with keys ACCESS_KEY_ID and SECRET_ACCESS_KEY exists in kube-system namespace and doesn't have the label kubeone.io/addon:. Remove the label if it exists. Otherwise, s3-exporter won't be functional. (#1880, @ahmedwaleedmalik)

Known Issues

  • Calico VXLAN addon has an issue with broken network connectivity for pods running on the same node. If you're using Calico VXLAN, we recommend staying on KubeOne 1.4 until the issue is not fixed. Follow #2192 for updates.

Checksums

SHA256 checksums can be found in the kubeone_1.5.0-beta.0_checksums.txt file.

Assets 7
Loading