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.
Talk to the engineer who will own your stack.
No account managers, no offshore handoff. Senior DevOps, direct. Tell us what you are dealing with and you get a straight answer.
Related News
GitHub Now Migrates GitLab Repositories in One Command
GitHub Enterprise Importer now handles GitLab migrations self-service, no consulting engagement needed. Repositories, issues, merge requests and releases move with one CLI extension. Here is what comes across, what you rebuild, and how to size the work.
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 & DevOpsOpenAI Is Deleting GPT-5 and o3 in December and the Teams That Pinned Their Models Break First
OpenAI notified developers on June 11, 2026 that six GPT-5 and o3 model snapshots leave the first-party API on December 11, 2026. Teams that pinned an exact dated snapshot ID, OpenAI's own recommended production practice, break loudly on that date, while floating aliases keep working but silently change behavior.