Releasenotes

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project will adhere to Semantic Versioning.

We use towncrier for the generation of our release notes file.

Information about unreleased changes can be found here.

General information about release upgrades are documented at How to Upgrade to a new TAROOK release.

v11.0.5 (2026-02-05)

Changed functionality

  • kubeadm manifest patch files supplied in /etc/kubernetes/kubeadm-patches are now applied on cluster initialization as well rather than Kubernetes upgrades only. (!2277)

Bugfixes

  • A proper InitConfiguration is now passed to kubeadm when reconfiguring the kube-apiserver for audit logging since we noticed that under certain circumstances the kubeadm.kubernetes.io/kube-apiserver.advertise-address.endpoint annotation got altered to contain an incorrect IP which then got used as advertized endpoint (rel #844).

    The error has been observed especially in bare metal clusters. In affected clusters, at least apply-k8s-core.sh or a full rollout via apply-all.sh must be first executed before performing a Kubernetes upgrade. (!2277)

  • Fixed a regression that was introduced with the refined kube-apiserver audit logging in v11.0.0 (!1956) which caused kubeadm to not consider manifest patch files which are e.g. used to configure yk8s.kubernetes.apiserver.memory_limit. (!2277)

v11.0.4 (2026-01-27)

Changed functionality

Bugfixes

  • A bug was fixed that caused issues when the same option was set in multiple places #846 (!2235)

  • Dropped the max length constraint on the yk8s.vault.cluster_name that was errorneously introduced with release v10.0.0. (!2235)

  • Fixed two errors that prevented the yk8s.load-balancing.lb_ports config option from being applied at all. (regression of v10.0.0) (!2235)

v11.0.3 (2025-12-09)

Bugfixes

v11.0.2 (2025-10-23)

Bugfixes

Other Tasks

v11.0.1 (2025-10-21)

Bugfixes

  • A bug in the migration script has been fixed (!2175)

v11.0.0 (2025-10-17)

Breaking changes

New Features

Changed functionality

Bugfixes

  • The type of yk8s.kubernetes.apiserver.audit_logs.policy has been changed such that individual values can be overwritten. (!1956)

  • A bug has been fixed which prevented to deploy rook-ceph in a different namespace than the default: yk8s.k8s-service-layer.rook.namespace. (!1998)

  • Ansible and Helm now don’t try to use user-wide (cache) directories anymore. (!2051)

  • Darwin as well as Linux on aarch64 are not supported by Tarook. Thus, they have been removed from the list of supported systems. (!2067)

  • Fixed the vault_v1 Ansible role to deploy the vault-backup ServiceMonitor only when monitoring is enabled via yk8s.kubernetes.monitoring.enabled. (!2069)

  • Adjust review link to new url (!2085)

  • Fixed an issue where regex validation of IP patterns did not work on macOS hosts. (!2104)

  • Deploying Vault on Kubernetes through yk8s.k8s-service-layer.vault requires cert-manager which is now documented and enforced at config evaluation. (!2114)

  • Fixed a bug which prevented etcd-backup to be deployed in a modified namespace: yk8s.k8s-service-layer.etcd-backup.helm.release_namespace. (!2122)

  • The .gitignore file of the cluster repository now includes the ‘managed by yk8s’ markers from cluster repo initialization already, not just after the first release migration. (!2131)

  • SSH host certificates are now always generated using the yaook/nodes Vault approle. Previously the orchestrator’s credentials were used when USE_VAULT_IN_DOCKER=true (see Developing with Vault) was set which prevented the use of unpriviledged Vault tokens. (!2132)

Changes in the Documentation

  • A note that nix (Nix) >= 2.9.0 is required has been added to Initialization. (!2063)

  • Documentation generation is restricted to the latest five major versions from now on. (!2102)

  • Merged the tutorials into the guides section (!2130)

Deprecations and Removals

Other Tasks

Misc