Skip to main content

Kubernetes 1.33

Support ended · upgrade now
Released
Latest Cluster Stack
1-33-v13
Last Updated
Support Ends

You're on Kubernetes 1.33, which stopped receiving updates on August 28, 2026. Moving to 1.36 puts you back on a maintained line, one tested step at a time.

Kubernetes 1.33 no longer receives updates

This line stopped receiving Cluster Stack releases on August 28, 2026. Reaching 1.36 takes three steps — 1.33 → 1.34 → 1.35 → 1.36 — because Kubernetes minor versions can't be skipped, and each step is tested end-to-end.

Start the upgrade

Cluster Stack releases for Kubernetes 1.33

  1. 1-33-v13

  2. 1-33-v12

  3. 1-33-v11

What Kubernetes 1.33 Shipped

Kubernetes 1.33 “Octarine” shipped 64 upstream enhancements. These are the ones 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.33 release announcement
Sidecar Containers Go Stable
Sidecars are a first-class pattern: they start before your app, run alongside it, and shut down after it exits — no more init-container workarounds.
Recursive Read-Only Mounts
Read-only volumes can now be read-only all the way down — submounts included — closing a long-standing gap in mount isolation.
Grow Service IP Space Live
Add Service CIDRs to a running cluster when ClusterIPs run out — no rebuild, no migration.
Job Success Policy
Declare an Indexed Job complete when the indices that matter succeed — leader-worker patterns without babysitting the whole Job.
nftables kube-proxy Backend
The nftables backend goes stable, with faster rule processing and better scaling than iptables on clusters with many Services.
CRD Validation Ratcheting
Tighten a CRD's schema without breaking what's already stored — stricter validation applies only to fields that change.
  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.33 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