Product Documentation

Appearance

EE: All cloud platforms

Kubernetes Version Support ​

INFO

This page is updated with each Yellowbrick release to reflect the current supported Kubernetes version window.

Each Yellowbrick release supports a window of Kubernetes minor versions on Amazon EKS, Azure AKS, and Google GKE. You can upgrade your Kubernetes control plane to any version within this window at any time; Yellowbrick recognizes and preserves your control plane version on your next Yellowbrick upgrade.

Supported Versions ​

The diagram and table below list the supported Kubernetes version window for each Yellowbrick release.

Yellowbrick ReleaseDefault Kubernetes VersionSupported Kubernetes VersionsRelease Date
7.4.41.341.34, 1.35, 1.36Oct 6, 2026
7.4.31.331.33Mar 18, 2026
7.4.21.321.32Mar 2, 2026

How the Support Window Works ​

  • Each Yellowbrick release includes a default Kubernetes minor version and supports two additional, newer minor versions.
  • Your control plane may run any minor version within the supported window for your installed Yellowbrick release.
  • Yellowbrick manages the Kubernetes version of your node pools (managed node groups) on Amazon EKS and Azure AKS: node versions are updated for you during Yellowbrick upgrades. On Google GKE this holds only provided that you keep up with Yellowbrick upgrades — see Google GKE Release Channel below for what happens if you fall behind.

Upgrading Your Kubernetes Control Plane ​

You can upgrade your control plane to any version within the supported window without waiting for a Yellowbrick release. Upgrade one minor version at a time, following your cloud provider's guidance. Your next Yellowbrick upgrade detects the control plane version and continues normally.

Amazon EKS ​

Upgrade the control plane from the Amazon EKS console, or with the AWS CLI:

bash
aws eks update-cluster-version --name <cluster-name> --kubernetes-version <version>

See Update the Kubernetes version for your EKS cluster in the AWS documentation.

Azure AKS ​

Upgrade the control plane from the Azure portal, or with the Azure CLI:

bash
az aks upgrade --resource-group <resource-group> --name <cluster-name> \
  --control-plane-only --kubernetes-version <version>

See Upgrade an AKS cluster in the Azure documentation.

Google GKE ​

Upgrade the control plane from the Google Cloud console, or with the gcloud CLI:

bash
gcloud container clusters upgrade <cluster-name> --master --cluster-version <version>

GKE upgrades the control plane one minor version at a time and does not allow skipping minor versions. See Upgrading a cluster in the Google Cloud documentation.

Google GKE Release Channel ​

Google Kubernetes Engine (GKE) clusters are enrolled in the Stable release channel. The control plane auto-upgrades within the channel; because Yellowbrick GKE clusters are regional, this does not affect the database. Node pools do not auto-upgrade — they move only during a Yellowbrick upgrade.

Control-plane maintenance runs in a daily window, by default 00:00 to 04:00 UTC. The window is always expressed in UTC because GKE stores an absolute time; the gcloud command line's account time zone convenience does not apply to the cluster. GKE requires a window of at least 4 hours, and at least 48 hours of maintenance availability in any 92-day rolling period, so a daily 4-hour window is the smallest sensible shape. You can change the start time and the length through the Deployer CLI reference.

When a Kubernetes minor reaches end of standard support (about 14 months after its release), Google upgrades the node pools itself, and that is a database outage. Stable carries no extended-support surcharge, so run a Yellowbrick upgrade within 14 months of your Kubernetes minor to avoid the forced node upgrade.

Extended release channel (opt-in) ​

If you cannot upgrade within that window, you can opt in to the Extended release channel instead. Extended buys roughly 10 further months before the forced node upgrade, at about $0.50 per cluster-hour on top of the standard $0.10 cluster management fee (roughly $360/month per cluster). The deadline itself does not move — Extended only makes it later, and billable. See the Deployer CLI reference for how to select it.

Planning Future Yellowbrick Upgrades ​

Future Yellowbrick upgrades require a release that includes your Kubernetes version in its supported window. When planning Kubernetes control plane upgrades, consult the table above to ensure your target version remains supported by upcoming Yellowbrick releases.

For Yellowbrick release support windows and end-of-support dates, see Product Release Lifecycle.