PuppyIP Resource Center
Cloud Operations 5 min Published 2026-11-21

GKE GCP-2026-088 Patch Checklist for Control Planes and Nodes

Google's November 20, 2026 update to GKE bulletin GCP-2026-088 adds Container-Optimized OS patch versions for GKE 1.32 and 1.33. Check the control plane and each node pool's version and image, then confirm which fixed patches your cluster can select.

GKE Security Patching GCP-2026-088 Container-Optimized OS

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • The two newly listed COS patch floors are 1.32.13-gke.3234000 and 1.33.13-gke.2533000.
  • The bulletin also lists COS patch floors for 1.34, 1.35, and 1.36. The November 20 update still lists GKE 1.37 on COS and Ubuntu node images as pending.
  • Google documents same-minor patches from a newer channel when available. Check the published fix and what your cluster can select separately.
  • Use actual control-plane versions, node versions, and node images to verify remediation. Check every node pool after the control plane upgrade.

Find the patch floor for your minor version

GCP-2026-088 covers CVE-2026-99288, a Linux kernel issue that can interrupt service. Google's November 20 update lists 1.32.13-gke.3234000 for Container-Optimized OS (COS) on GKE 1.32 and 1.33.13-gke.2533000 for COS on GKE 1.33.

The bulletin also lists COS floors of 1.34.13-gke.1091000, 1.35.10-gke.1155000, and 1.36.6-gke.1189000. Compare within each minor version. The November 20 update still lists GKE 1.37 on COS and Ubuntu node images as pending. A note farther down still lists 1.32 and 1.33 as pending. Use the dated update for those two lines.

Inventory the control plane and each node image

In GKE cluster details, record the location, release channel, control-plane version, and the running GKE version and node image for each pool. A cluster can have multiple image types, so check each pool on its own. Match the listed COS patches to COS pools and check Ubuntu's own patch status for Ubuntu pools.

For example, a control plane may show 1.33.13-gke.2533000 while a COS pool still shows an earlier build on the same minor line. Track that pool's upgrade separately. Record a separate image and patch status for any Ubuntu pool. Mark each pool as at the patch floor, awaiting an upgrade, or awaiting its image update.

Confirm which version your cluster can use

Check the upgrade choices for your cluster's location and release channel. Patch versions enter the channels over time, so use the cluster's available versions to establish what you can select. If you need to upgrade early, check node and workload compatibility in a test environment and use your regular change window.

Google documents using gcloud CLI or the GKE API to choose an available patch from a newer channel when the target minor version is present in the current channel and the control plane already runs that minor version. Follow the ordinary upgrade process for a minor-version change.

Verify the control plane and workers after upgrading

Control-plane and node upgrades run as separate operations. On Standard clusters, check actual node versions and upgrade progress for each pool. On Autopilot clusters, monitor GKE's managed worker upgrade and confirm the running versions. If there are maintenance exclusions, check their effect on this cluster's upgrade schedule.

After the upgrade, read the control-plane and node inventory again. Verify the intended images and patch versions, and check normal workload health. Keep any still-upgrading pool or pending image marked as incomplete. If a patch version is missing, check the cluster's upgrade notifications and record the version list and observation time.

Sources

Frequently Asked Questions

Why is the patch in the bulletin missing from my cluster's version choices?

GKE introduces builds across release channels over time. Check versions available for the cluster's location and its upgrade notifications, then see whether the documented newer-channel patch conditions apply.

What if I can only see the control plane in production?

Have an operator with node-pool read access confirm the image, running version, and upgrade state in each pool. The control-plane version covers only the control plane.

Should I reproduce the issue with network traffic to confirm the fix?

You can confirm patch status from the advisory, node images, and actual running versions. Check workload health with your usual probes after the upgrade and keep the two observations separately.