Maintenance windows schedule change; exclusions create bounded freezes

Use a recurring window for normal work and short exclusions for known business events. GKE still requires maintenance availability and exclusions cannot bypass end-of-support indefinitely.

Window

Defines when eligible automatic maintenance may start.

Exclusion scope

Can block all upgrades or selected upgrade types for a bounded period.

Retail freeze

Shopwave excludes upgrades around its major sale, then restores normal cadence.

External dependencies

Some underlying Compute Engine maintenance is outside GKE maintenance policy.

A freeze is a risk transfer: fewer planned changes now, more accumulated change later.

Maintenance windows schedule change; exclusions create bounded freezes

Maintenance windows and exclusions is easiest to understand by separating the Kubernetes contract from the Google Cloud implementation. GKE maintenance policies influence the timing of automatic upgrades and some node or network changes. Release-channel clusters receive more granular exclusion scopes. The Kubernetes objects stay familiar, but GKE supplies controllers, infrastructure and safe defaults around them. This is why a team can move from an on-premises cluster without rewriting every workload, while still needing to redesign networking, identity and operational ownership for the cloud environment.

A useful inspection step is `gcloud container clusters describe shopwave-prod --format='yaml(maintenancePolicy)'`. Read the output as evidence, not as a ritual: first confirm the desired object exists, then look at status conditions, events and the Google Cloud resource it represents. In production, capture the expected result in a runbook or automated check so an operator can distinguish slow reconciliation from a configuration error.

Production gotcha: You must leave sufficient maintenance availability, and emergency or dependency maintenance might not respect the preferred window. The safe habit is to verify quotas, regional availability and feature support against current Google Cloud documentation before rollout. Upgrade strategies determine how nodes turn over.