Skip to main content

Kubernetes 1.34

Support ends soon · upgrade now
Released
Latest Cluster Stack
1-34-v12
Last Updated
Support Ends

You're on Kubernetes 1.34 — still safe today, but support ends October 27, 2026, about 6 days away. You should upgrade now: reaching 1.36 means moving up through 1.35 first.

Still supported today — but it’s time to upgrade

You can update to the latest 1.34 Cluster Stack release, but support ends October 27, 2026. Reaching 1.36 takes two steps — 1.34 → 1.35 → 1.36 — because Kubernetes minor versions can't be skipped, and each step is tested end-to-end. Start now.

Start the upgrade

Cluster Stack releases for Kubernetes 1.34

  1. 1-34-v12

  2. 1-34-v11

  3. 1-34-v10

What Kubernetes 1.34 Shipped

The upstream Kubernetes 1.34 changes that are on by default in your clusters. 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.34 release announcement
Dynamic Resource Allocation Goes GA
Request GPUs and custom hardware with structured claims the scheduler actually understands — the foundation for accelerator workloads.
Ordered Namespace Deletion
Namespace teardown now deletes Pods before the resources they depend on — no more NetworkPolicy vanishing while workloads still run.
Recover From Failed Volume Expansion
A too-big resize no longer wedges the volume — shrink the request back and retry without recreating the PVC.
Native Connection Draining
The sleep action for PreStop and PostStart hooks goes stable — drain connections on shutdown without shipping a sleep binary in the image.
Change Volume Class In Place
VolumeAttributesClass goes stable: modify a volume's IOPS or throughput tier without migrating the data.
Streaming List Responses
Large list responses stream instead of buffering, cutting API server memory spikes on clusters with many objects.
  1. Kubernetes 1.36 Cluster Stack 1-36-v7
  2. Kubernetes 1.35 Cluster Stack 1-35-v6
  3. Kubernetes 1.34 Cluster Stack 1-34-v12

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

Upgrade Kubernetes 1.34 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