Cluster Versions
Kubernetes Cluster: Versions & Change Logs
The platform provides a pre-packaged Kubernetes Cluster solution with automated installation, scaling, management, and lifecycle tooling. New Kubernetes versions are periodically added for new cluster deployments together with updated Kubernetes ecosystem components and compatibility fixes.
Easy Start
Install Kubernetes through the platform package instead of assembling the cluster manually.
Hyper Scalability
Combine Kubernetes with platform vertical and horizontal scaling capabilities.
Simplified Management
Manage the environment from one platform dashboard with built-in Web SSH and automation tools.
Multi-Cloud Availability
Use the package across supported cloud regions and infrastructure providers.
Flexible Automation
Integrate DevOps workflows through API and Cloud Scripting capabilities.
Cost Efficiency
Consume and scale resources according to actual demand.
On this page
Recent Kubernetes Versions
The source change log currently lists the following recent Kubernetes releases as versions added for new cluster installations.
| Kubernetes Version | Status in Change Log | Notable Notes |
|---|---|---|
| 1.33.12 | Added for new cluster installations | Updated major bundled components and fixed Rancher compatibility. |
| 1.32.13 | Added for new cluster installations | Updated ingress, dashboard, Helm, K9s, container runtime, CNI, and related tools. |
| 1.31.14 | Added for new cluster installations | Includes refreshed Kubernetes utilities and Rancher compatibility fix. |
| 1.30.14 | Added for new cluster installations | Updated ingress, dashboard, MetalLB, Helm, K9s, containerd, and CNI components. |
| 1.29.14 | Added for new cluster installations | Updated cluster-management and networking components. |
Important: The exact versions visible in the Kubernetes installation wizard can depend on the current package release and hosting provider. The change log records versions introduced over time; it should not be interpreted as a guarantee that every historical release remains selectable for a new cluster.
Bundled Component Versions
Each Kubernetes release can also update the supporting tools that are bundled with the cluster package. Recent change-log entries include components such as:
Ingress NGINX
Recent releases list
ingress-nginx 1.11.2.
Kubernetes Dashboard
Recent releases list
kubernetes-dashboard 2.7.0.
MetalLB
Recent releases list
metallb 0.14.8.
Helm
Newer entries include Helm 3.x releases, with the exact version depending on Kubernetes package generation.
K9s & Stern
Command-line cluster-management and log-following utilities are updated together with Kubernetes releases.
containerd & CNI
Recent releases use the containerd runtime and updated CNI plugin packages.
Bundled component versions are part of the Kubernetes package lifecycle. Upgrading Kubernetes can therefore also update ingress, monitoring, networking, dashboard, CLI, container-runtime, and other cluster components.
Version Selection
The platform introduced a Kubernetes version selector in the installation window so users can choose among the supported recent Kubernetes versions when creating a new cluster.
Version selector behavior: The source release history notes that the installation window was designed to show the three latest Kubernetes versions in descending order. The actual choices visible in a live platform may vary as the package evolves.
Compatibility and Upgrade Notes
Kubernetes upgrades can require changes to bundled components, deprecated APIs, ingress resources, runtime settings, storage integrations, and third-party management tools.
- Some older Kubernetes releases temporarily disabled Rancher integration until compatibility was restored.
- Traefik 1.x was replaced by Traefik 2.x, which introduced architectural and custom-resource differences.
- Upgrades can require migration away from deprecated Kubernetes APIs or annotations.
- The platform has adjusted upgrade logic over time to handle unknown components and dependency changes more safely.
- Container runtime and networking components can change between major package generations.
Before upgrading an existing cluster, review the dedicated Kubernetes Cluster Upgrade documentation and check custom ingress resources, operators, CRDs, storage classes, and third-party tools for compatibility with the target Kubernetes version.
Release Notes Archive
The version history contains a long archive of Kubernetes releases, including multiple patch versions across the 1.15.x through 1.33.x generations. Each entry can contain one or more of the following changes:
- New Kubernetes version availability for fresh cluster installations.
- Updated Kubernetes ecosystem components.
- Ingress-controller changes.
- Dashboard, Helm, monitoring, storage, and networking updates.
- Compatibility fixes for Rancher, GitLab, Jaeger, cert-manager, and other integrations.
- Cluster upgrade improvements and bug fixes.
How to use the archive: Use the change log when you need to understand when a Kubernetes version or integration was introduced, which supporting components changed, or whether a historical compatibility issue was addressed.