Kubernetes v1.35.10 was published on October 28, 2026 as a stable release, not a prerelease. The GitHub release body carries no change list of its own. It points to the announce list and to the 1.35 CHANGELOG file.
The full release notes and downloads are on the GitHub release page.
What the release page actually says ¶
The notes are two sentences long. They link to the kubernetes-announce mailing list and to CHANGELOG-1.35.md in the repository. They say additional binary downloads are linked from that CHANGELOG.
That is all. There is no list of fixed bugs, no CVE references, and no dependency bump summary in the release text. This post does not invent any. If a specific fix matters to you, the CHANGELOG is the only source cited by the release.
This is normal for a patch tag in a minor line. The v1.35 branch gets a new tag, and the detail lives in a generated file. The cost falls on the reader. You have to open the file and read the entries for v1.35.10 yourself.
How to read the 1.35 CHANGELOG for this tag ¶
The CHANGELOG is one file for the whole 1.35 line, so older patch sections sit next to the new one. Scope your reading.
- Find the
v1.35.10heading and read only that section. - Check the “Changes by Kind” groupings for bug fixes first. Patch releases are mostly that.
- Search the section for the components you run:
kube-apiserver,kubelet,kube-proxy, your CSI and CNI integration points. - Look for anything marked as a security fix or a behavior change. Treat those as a reason to schedule the rollout sooner or to test longer.
The CHANGELOG for 1.35 is linked from the release notes, so that URL is the one to open.
Rolling a patch through a cluster ¶
Nothing in the release text mentions breaking changes. Still, a patch bump touches every control plane binary and every node, so the usual order applies.
- Upgrade the control plane first, one member at a time, and check
kube-apiserverhealth between steps. - Upgrade nodes afterward. Cordon and drain, replace the
kubelet, uncordon. - Keep kubelet skew within the supported window relative to the API server. A patch bump inside 1.35 does not change that rule.
- Pin image tags and binary checksums in your build. If you pull artifacts from the CHANGELOG links, verify them against the published sums.
Winners and losers are easy to name. Teams that already track a single 1.35 patch version in code get a short diff and a quick rollout. Teams with a mix of patch levels across clusters have the harder job, since they have to read several CHANGELOG sections to see what they skipped.
Upgrade notes ¶
The release notes state no breaking changes and no migration steps. They state nothing at all about content, so absence of a warning here is not evidence that the CHANGELOG is clean. Read the v1.35.10 section before you promote the tag past staging. Run your normal conformance and workload smoke tests on a canary cluster first.
If you consume Kubernetes through a managed service, the provider decides when v1.35.10 becomes available. Check their version matrix instead of assuming the upstream date applies.
Where to get it ¶
- Release page: v1.35.10
- Repository: https://github.com/kubernetes/kubernetes
- Tag:
v1.35.10