Release notes

These release notes highlight user-visible changes and bug fixes for Cloudfleet’s Kubernetes Engine (CFKE). Beyond the features listed here, Cloudfleet is frequently updated for improved stability, performance, and security. You may notice your CFKE version number increasing without any visible features as we continuously enhance the underlying platform.

July 12, 2025

July 7, 2025

  • The IAM permissions required for accessing private container registries have been updated based on the control plane region. Please refer to the updated Private container registries documentation for the latest IAM permissions required.

July 3, 2025

  • CFKE’s Cilium deployment now allows running other CNI plugins alongside it. This change enables installation of software like Istio CNI node agent. See the new Istio deployment tutorial for details on how to deploy Istio with Cilium.
  • Hetzner Cloud private network is now adjusted in a way to leave enough IP space to create a additional subnetwork. This allows creating a subnetwork to use with vSwitches.

June 28, 2025

  • The cfke.io/instance-family label is now available for node auto-provisioning. This label allows you to specify the instance family for node auto-provisioning while leaving the instance size selection to CFKE. For example, you can use cfke.io/instance-family: ccx to select the Hetzner Cloud CCX (dedicated CPU) instance family. This feature provides more flexibility in choosing the instance family while still allowing CFKE to determine the optimal instance size.

June 26, 2025

  • The first European region, europe-central-1a, is now available for CFKE users. Located in Frankfurt, Germany, this region offers low-latency access to European customers and supports a wide range of instance types and services. Check out the launch blog post for more details.
  • CFKE control plane is now also available with an IPv6 address. This change is currently only available in the europe-central-1a region and will be rolled out to other regions soon.

June 19, 2025

  • Hetzner instances are now created with an IPv6 address by default in addition to the IPv4 address. This change enhances network connectivity and allows for better integration with modern networking standards.
  • Fixed a bug where Pro cluster control plane replicas were mistakenly placed in the same availability zone. This fix ensures that control plane replicas are distributed across different availability zones, improving reliability and fault tolerance.

May 27, 2025

  • CFKE now supports limiting control plane access to specific IP addresses. This feature is only available on the Enterprise plan.

May 26, 2025

  • CFKE now supports internal load balancing for Hetzner Cloud. This feature allows you to create load balancers that are only accessible to other instances within the same network. For more details, see the updated Exposing applications to the internet documentation.
  • CFKE now supports Egress Gateways. This feature allows you to route outbound traffic from the cluster through dedicated nodes, providing better control over egress traffic and enabling advanced routing capabilities. For more details, see the Egress Gateways documentation.
  • CFKE now supports the Metrics API by default. This enables Kubernetes features like Horizontal Pod Autoscaler to work out of the box without additional configuration.

May 22, 2025

  • CFKE now supports overriding the Hetzner Load Balancer scale by specifying networking.cfke.io/hetzner-load-balancer-scale in the Service specification. Previously, CFKE automatically determined the scale based on the number of nodes in the cluster. You can now specify the desired scale for the Hetzner Load Balancer, allowing for more granular control over load balancing behavior. See the updated Exposing applications to the internet documentation for details.

May 19, 2025

  • Fixed a bug where non-administrators were unable to view the cluster nodes in the Cloudfleet console.

May 1, 2025

  • CFKE upgraded Kubernetes versions to 1.30.12, 1.31.8, and 1.32.4.

April 24, 2025

  • Self-managed nodes are now garbage collected one hour after their last heartbeat to the CFKE control plane. This change helps clean up unused nodes and free up resources in the cluster. Garbage collected nodes will rejoin the cluster once they communicate with the CFKE control plane again.

April 13, 2025

  • CFKE upgraded Kubernetes versions to 1.30.10, 1.31.6, and 1.32.2. With this release, support for 1.29 was dropped and 1.32 was introduced with its latest patch version.

March 31, 2025

  • CFKE now cleans up unused resources like firewalls and networks from Hetzner Cloud when there are no nodes remaining in the cluster.
  • Fixed an issue with GCP where spot instances were not removed after preemption but remained in a stopped state. Spot instances are now properly removed from the project after preemption.

March 3, 2025

  • Built-in CoreDNS no longer uses ports 8080, 8081, and 9153 on the host network. This change enables you to use these ports for your own applications without conflicts.

February 5, 2025

  • CFKE’s Cilium version was upgraded to 1.17.0.

February 4, 2025

  • Fixed a race condition that caused issues when a node belonging to a deleted Fleet also became NotReady and got stuck in the cluster.

February 1, 2025

  • Fixed an issue where nodes hosted on Oracle Cloud Infrastructure (OCI) had problems with in-cluster DNS resolution. This fix resolves side effects that affected commands like kubectl exec and kubectl logs.
  • Managed Load Balancing is now Generally Available (GA). This feature allows you to create and manage load balancers for your services more efficiently. For more details, see the Exposing applications to the internet documentation.

January 28, 2025

  • CFKE now has topology-aware load balancing enabled by default. This feature allows Kubernetes to route traffic to the closest node in the cluster, improving performance and reducing latency. For more details, see the Kubernetes documentation on Topology Aware Routing.

January 10, 2025

  • BGP Data Plane is now available for CFKE clusters by default. This feature allows you to use BGP in on-premises locations to expose cluster services to the LAN or WAN. For more details, see the On-premises load balancing with BGP documentation.

January 7, 2025

  • Managed NVIDIA driver installation is now available for self-managed nodes. This feature allows you to install NVIDIA drivers on your self-managed nodes without manual installation. For more details, see the updated Self-managed nodes documentation.

January 2, 2025

  • NVIDIA Device plugin is now part of CFKE clusters and runs on each node with NVIDIA hardware. This plugin enables Kubernetes to schedule GPU workloads on nodes with NVIDIA GPUs. For more details, see the updated GPU-based workloads documentation.

December 8, 2024

  • CFKE upgraded Kubernetes versions to 1.29.3, 1.30.7, and 1.31.3. With this release, Kubernetes 1.30 and 1.31 were introduced with their latest patch versions.

November 30, 2024

  • Fixed an issue with ARM instance scheduling.

October 22, 2024

  • Cloudfleet General Availability Launch: We’re thrilled to announce that Cloudfleet is now Generally Available (GA)! Cloudfleet is now ready for production workloads. Thank you to our early adopters and beta users for their valuable feedback. We’re excited to see how you’ll use Cloudfleet to build, deploy, and manage your cloud-native applications at scale.
On this page