Skip to main content

Kubernetes 1.35

Supported · safe to stay
Released
Latest Cluster Stack
1-35-v6
Last Updated
Support Ends

You're on Kubernetes 1.35 — a supported version, so there's nothing you need to do today. This page shows what 1.35 gives you, how long it stays supported, and how to move up to 1.36 when you're ready.

Continue receiving updates, then move to 1.36

You can always update to the latest 1.35 Cluster Stack release without leaving this version. When you're ready to move on, there's a tested, step-by-step path to Kubernetes 1.36 — no jumping across untested versions.

Start the upgrade

Cluster Stack releases for Kubernetes 1.35

  1. 1-35-v6

  2. 1-35-v5

  3. 1-35-v4

What Kubernetes 1.35 Shipped

Kubernetes 1.35 shipped 60 upstream enhancements. These are the ones enabled by default in your Cluster Stack — beta and alpha features stay behind feature gates unless you turn them on.

These are upstream Kubernetes capabilities. Availability can depend on feature gates and the Cluster Stack configuration.

Read the Kubernetes 1.35 release announcement
In-Place Pod Resizing
Adjust a Pod's CPU and memory budget without a restart — no redeploy, no dropped connections.
Strict Supplemental Groups
Control exactly which supplemental groups a Pod's processes get — surprise group memberships from the container image no longer leak in.
Reliable Pod Update Tracking
Pod generation goes stable: observedGeneration tells you whether the kubelet has actually acted on your latest change.
Kubelet Drop-In Configuration
Manage kubelet settings as layered drop-in files instead of one monolithic config — safer automation for node fleets.
Hand Jobs to External Queues
The Job managed-by mechanism goes stable — delegate Job lifecycle to controllers like Kueue for multi-cluster queueing.
Keep Traffic on the Node
PreferSameNode traffic distribution goes stable — Services route to a local endpoint when one exists, falling back when it doesn't.
  1. Kubernetes 1.36 Cluster Stack 1-36-v7
  2. Kubernetes 1.35 Cluster Stack 1-35-v6

From Cluster Stack 1-35-v1, the update path leads to 1-35-v6, and the upgrade path continues to 1-36-v7.

Upgrade Kubernetes 1.35 to 1.36

Every change to a cluster's Kubernetes version comes through a Cluster Stack release, never a patch to a running node. An update keeps the cluster on the same Kubernetes minor version; an upgrade moves it to a newer one. Both run a tested, automated path.

Updates carry maintenance work: security patches, bug fixes, and component bumps that do not change how Kubernetes behaves.

Upgrades are where new Kubernetes behavior lands, along with new Syself features, API changes, and the larger compatibility shifts between minor versions.

Explore Tested Upgrade Paths
  • Cloud servers are replaced, bare-metal ones are reprovisioned
  • Kubernetes, the components, and the node image move together
  • Every node runs a tested stack version

Related Resources

Go deeper on how Cluster Stacks are built, how clusters move between versions, and how Syself runs them day to day.

See All