Kubernetes 1.35 remained in active support as 1.35.2 shipped in late February 2026, giving platform teams a clearer current upgrade target.
Kubernetes 1.35.2 Becomes the Latest Supported Patch
By late February 2026, Kubernetes 1.35.2 had become the latest patch in the actively supported 1.35 release line. For infrastructure teams, that makes 1.35 a more relevant target than the older 1.31 and 1.32 discussions that still appear in many blog roundups.
Why This Matters
The most useful takeaway is not just that another patch landed, but that the current supported branch moved forward again. Teams planning upgrades should align internal testing, admission policy checks, and add-on compatibility against the active release train rather than treating older minor versions as their default reference point.
Upgrade Planning for 2026
A practical 2026 Kubernetes review should include:
- control plane and node version skew checks
- CNI, CSI, and ingress-controller compatibility
- policy engine validation for Gatekeeper or Kyverno
- Helm chart testing against the active API surface
- workload rollout verification for stateful and batch jobs
Operational Recommendation
If your production clusters are still anchored on much older minors, use 1.35 as the baseline for testing and planning. Even when you do not upgrade immediately, keeping engineering docs aligned with the actively supported branch reduces drift and avoids repeating outdated recommendations in platform runbooks.
Or read how we handle it in Kubernetes Management.
Related News
Docker Desktop 4.36 Introduces Resource Saver Mode
Docker Desktop 4.36 adds resource saver mode that reduces CPU and memory usage by up to 80% when containers are idle. Key update for developers.
Server & DevOpsGitHub Ships Stacked Pull Requests and One Limitation Decides Whether Your Team Can Actually Use Them
On July 30, 2026 GitHub put stacked pull requests into public preview: an ordered chain of dependent PRs where each layer targets the one below, reviewed separately and merged bottom up, with the branches above rebasing themselves as lower ones land. It is the workflow Graphite built a business on, now native and free. The catch is in the docs rather than the announcement, and it rules the feature out for a whole class of work: all branches must live in the same repository, so cross-fork stacks are not supported at all.
Server & DevOpsKubernetes 1.35 Is the Last Version That Runs containerd 1.x and Most Clusters Have Not Noticed
Kubernetes 1.35, released December 17, 2025, is the last minor release whose runtime support still includes a containerd 1.x version. To upgrade beyond it, every node has to move to containerd 2.x first, and containerd 1.7 itself reaches end of support in September 2026. The trap is not a single date: it is the upgrade path, and most clusters have not noticed because nothing is broken yet.