Komodor is an autonomous AI SRE platform for Kubernetes. Powered by Klaudia, it’s an agentic AI solution for visualizing, troubleshooting and optimizing cloud-native infrastructure, allowing enterprises to operate Kubernetes at scale.
Proactively detect & remediate issues in your clusters & workloads.
Easily operate & manage K8s clusters at scale.
Reduce costs without compromising on performance.
Guides, blogs, webinars & tools to help you troubleshoot and scale Kubernetes.
Tips, trends, and lessons from the field.
Practical guides for real-world K8s ops.
How it works, how to run it, and how not to break it.
Short, clear articles on Kubernetes concepts, best practices, and troubleshooting.
Infra stories from teams like yours, brief, honest, and right to the point.
Product-focused clips showing Komodor in action, from drift detection to add‑on support.
Live demos, real use cases, and expert Q&A, all up-to-date.
The missing UI for Helm – a simplified way of working with Helm.
Visualize Crossplane resources and speed up troubleshooting.
Validate, clean & secure your K8s YAMLs.
Navigate the community-driven K8s ecosystem map.
Who we are, and our promise for the future of K8s.
Have a question for us? Write us.
Come aboard the K8s ship – we’re hiring!
Discover our events, webinars and other ways to connect.
Here’s what they’re saying about Komodor in the news.
Join the Komodor partner program and accelerate growth.
The latest Kubernetes version depends on whether you are checking upstream Kubernetes or a managed service such as GKE, EKS, or AKS. Use this table as a quick reference, then verify provider-specific availability before upgrading production clusters.
As of April 2026, the latest upstream Kubernetes release is Kubernetes v1.36.0. However, the latest available version depends on where you run Kubernetes. Managed Kubernetes providers such as GKE, EKS, and AKS follow their own rollout schedules, support windows, and patch availability.
Managed Kubernetes versions vary by region, release channel, and provider rollout schedule. Always verify availability in your own cloud provider account before planning an upgrade.
Kubernetes versions are identified by three numerical components: major, minor, and patch. This system follows semantic versioning (semver) rules, allowing users to understand the level of changes in each release. The versioning system helps in managing the evolution of Kubernetes, addressing bugs, adding features, and improving user experience.
As mentioned above, there are three types of version releases in Kubernetes:
The Kubernetes project maintains release branches for the most recent three minor versions. As of April 2026, the actively maintained upstream Kubernetes release branches are 1.36, 1.35, and 1.34.
1.36
1.35
1.34
This matters because supported Kubernetes versions continue to receive patch releases, bug fixes, and security updates. Running an unsupported version can increase operational risk, especially for production clusters that depend on stable APIs, compatible add-ons, and timely vulnerability fixes.
1.33
Managed Kubernetes providers such as GKE, EKS, and AKS may use different availability windows, support policies, and upgrade rules. Always check your provider’s version lifecycle before planning a production upgrade.
Having the latest version of Kubernetes is essential for several reasons:
New versions fix vulnerabilities discovered in earlier releases. Neglecting updates can expose clusters to attacks, compromising the integrity and confidentiality of applications. Security enhancements are often included in new releases, providing better default settings and new features to improve cluster security.
Each Kubernetes release introduces new features and improvements. Updating enables access to these features, allowing users to leverage the latest advancements for better performance, usability, and reliability. In addition, new features often address user feedback, allowing the Kubernetes project to respond to new use cases and requirements.
Updates often include optimizations that improve the performance and stability of Kubernetes. These enhancements contribute to smoother operations and reduced downtime. By upgrading, users can take advantage of these improvements, ensuring their deployments run more efficiently and are less prone to failure.
Itiel Shwartz
Co-Founder & CTO
In my experience, here are tips that can help you better manage Kubernetes versions:
Regularly automate checks for new Kubernetes versions to stay informed on available updates.
Ensure all dependencies, including add-ons and plugins, are compatible with new Kubernetes versions before upgrading.
Use canary clusters to test new Kubernetes versions and configurations before rolling out to production environments.
Set up automated backups of your clusters and configurations to prevent data loss during upgrades.
Prefer managed node groups for easier updates and reduced operational overhead.
You can find the latest version of Kubernetes in the official releases page. This page provides links to the schedule and changelog of the latest Kubernetes minor versions.
Visit the Kubernetes releases page
Google Kubernetes Engine does not expose Kubernetes versions in the same way as upstream Kubernetes. GKE versions include a provider-specific suffix, such as -gke, and availability depends on the selected release channel, cluster type, region, and rollout status.
-gke
As of April 2026, GKE release notes list 1.36.0-gke.1379000 in the Rapid channel. This does not necessarily mean every production GKE cluster should immediately move to that version. The Rapid channel receives newer Kubernetes versions earlier, while Regular and Stable channels are better suited for teams that want a more conservative rollout path.
1.36.0-gke.1379000
For production environments, check:
Visit the Google Kubernetes Engine release notes to confirm the latest available GKE versions before planning an upgrade.
Amazon EKS follows its own Kubernetes version lifecycle, so the latest upstream Kubernetes version is not always immediately available in EKS. Before upgrading, teams should check both the Kubernetes minor version and the EKS platform version.
As of April 2026, Amazon EKS lists Kubernetes 1.35, 1.34, and 1.33 in standard support. Older versions may still be available under extended support, but extended support should be treated as a temporary bridge rather than a long-term operating model.
For EKS clusters, check:
Visit the Amazon EKS Kubernetes versions page to confirm currently supported EKS versions.
Azure Kubernetes Service publishes a Kubernetes release calendar that shows upstream release timing, AKS preview timing, GA availability, end-of-life dates, and platform support. This makes AKS version planning slightly different from checking the latest upstream Kubernetes release.
As of April 2026, AKS lists Kubernetes 1.36 with upstream release in April 2026, AKS preview in May 2026, GA in June 2026, and end of life in June 2027. AKS 1.35 is already listed as GA, with end of life in March 2027.
For AKS clusters, check:
Visit the AKS supported Kubernetes versions page to confirm current availability, support status, and version-specific breaking changes.
To check your Kubernetes version, run the following command:
kubectl version
This command displays the client and server versions, showing the version of kubectl and the Kubernetes cluster it’s communicating with. It’s useful for troubleshooting and ensuring compatibility between kubectl and the Kubernetes cluster.
A Kubernetes release follows a structured process of approximately four months, as shown in the following diagram:
Source: Kubernetes
Each release follows three phases:
After the Stabilization phase, the release enters a brief period where final adjustments and documentation updates are made. Following this, the new version is officially released, and the master branch re-opens for development towards the next milestone.
There are several measures that can help ensure Kubernetes is always updated to the latest version while minimizing the impact to your system.
Before upgrading, review the release notes for the target Kubernetes version. These notes detail new features, improvements, deprecations, and bug fixes. Understanding these changes helps in assessing the impact of the upgrade on your deployments.
Release notes also provide critical information on breaking changes and migration steps, if necessary. This preparation ensures a smooth upgrade process, minimizing disruptions and leveraging new Kubernetes functionalities effectively.
Related content: Read our guide to Kubernetes Upgrades.
Upgrading Kubernetes in a staging environment before rolling the update to production is crucial. This testing phase identifies potential issues and incompatibilities with applications or configurations. It allows for adjustments and planning to ensure a seamless transition during the actual upgrade.
Emulating the production environment as closely as possible during testing provides confidence in the upgrade process. It ensures that the new Kubernetes version operates as expected under realistic conditions.
Implementing gradual rollouts decreases risk during upgrades. Start with less critical environments, progressively moving to more critical ones. This phased approach allows for monitoring effects and addressing any issues before wider deployment.
Automated Kubernetes management tools streamline the upgrade process, reducing manual efforts and errors. Tools like Kubernetes Operations (kops), Kubeadm, and cloud provider managed services can automate many steps of the upgrade, or even automate the entire cluster upgrade process.
Skipping versions or ignoring prerequisites can introduce issues. Following the recommended path outlined in Kubernetes documentation or by cloud providers ensures compatibility and stability. Familiarizing yourself with upgrade paths and dependencies prevents potential problems, ensuring a successful upgrade.
Upgrading may require adjustments to deployments and configurations to leverage new features or maintain compatibility. Reviewing and updating resource definitions, manifests, and other settings is essential. Making necessary adjustments ensures that applications benefit from the latest Kubernetes improvements and functionalities.
Keeping Kubernetes versions current is not just a release management task. For platform, DevOps, and SRE teams, it means knowing which clusters are approaching end of life, which APIs are deprecated, where configuration drift has appeared, and whether workloads, add-ons, and node pools are ready for the next upgrade.
Komodor helps teams manage this complexity across Kubernetes environments by providing visibility into cluster health, version status, deprecated APIs, drift, workload changes, and upgrade-related risks from one place.
Komodor is an autonomous AI SRE platform for Kubernetes, powered by Klaudia, built to help teams visualize, troubleshoot, and optimize cloud-native infrastructure at scale.
For Kubernetes version management and upgrade readiness, Komodor can help teams:
Instead of treating Kubernetes upgrades as isolated maintenance windows, Komodor helps teams turn version management into a continuous operational practice. Teams can see which clusters need attention, understand upgrade blockers earlier, and troubleshoot issues faster when version changes affect production workloads.
Ready to improve Kubernetes upgrade readiness across your clusters? Schedule a demo or start a free trial with Komodor.
Use kubectl version to see the kubectl client version and the Kubernetes server version. You can also run kubectl get nodes -o wide to inspect node-level version details.
Not always immediately. For production clusters, the safer rule is usually to stay on a supported minor version and apply the latest available patch release, then plan minor upgrades after testing compatibility with workloads, add-ons, and provider constraints.
Version skew defines which Kubernetes component versions can safely run together. For example, kubelet must not be newer than kube-apiserver and can be up to three minor versions older.
Share:
Gain instant visibility into your clusters and resolve issues faster.
May 12 · 9:00EST / 15:00 CET · Live & Online
🎯 8+ Sessions 🎙️ 10+ Speakers ⚡ 100% Free
By registering you agree to our Privacy Policy. No spam. Unsubscribe anytime.
Check your inbox for a confirmation. We'll send session links closer to May 12.
