Kubernetes 1.30 was an upgrade planning reminder

Kubernetes 1.30 was a reminder that cluster upgrades are calendar work.

The release is only the date. The plan needs an owner, a test window, affected workloads, and a rollback path:

cluster_upgrade_plan:
  version: "1.30"
  owner: platform
  test_window: "two weeks"
  checks:
    - version skew
    - ingress behavior
    - storage class behavior
    - rollout restart
    - workload autoscaling

A preview cluster can expose ingress and storage changes before they become an application outage. Run a deployment, roll it back once, watch the metrics, and widen the blast radius only after the checks are boring.

The release is not the work. The work is knowing which workloads care before the new version is live. A calendar with dates and owners is what keeps the upgrade from becoming surprise application work.