Upgrades, recovery paths and the full bill

Part 13 · Further improvements

Upgrades, recovery paths and the full bill

Prerequisites: 04-eks-model, 09-release-reliability, 12-observability

Inventory and rehearse, prepare compatibility, upgrade control plane, roll nodes and add-ons, validate behavior, then choose a documented recovery path if needed. — A high-level workflow, not an executable runbook. Some add-ons need preparation before the control-plane step. Rollback has eligibility and compatibility limits and does not revert data or all add-ons. [S22] [S31] [S38]

Five cost rows cover cluster support, compute, networking, storage and operations. Standard support is 73 dollars for a 730-hour illustrative month, extended support 438 dollars. — Published standard cluster-support rates retrieved on 2026-10-10. Region, partition, features, support tiers and resource usage can change the bill. No compute-price estimate is asserted. [S23]

Learning objective and upgrade mechanism verified

Inventory removed APIs, admission webhooks, CRDs, nodes and add-ons. Rehearse in a representative non-production environment. Follow the EKS procedure for the control plane and compatible components. Standard add-on updates are not automatically completed merely because the control plane was upgraded; Auto Mode changes some operational responsibilities.

[S22] [S31] [S15]

Current recovery boundary verified

The retrieved EKS documentation describes a conditional version rollback: initiate within seven days of an in-place upgrade, return only to the previous minor version and satisfy eligibility and compatibility checks. It preserves data and does not roll back all add-ons or non-Auto-Mode compute for you. Check current supported versions and the detailed prerequisites before relying on it. After that window, a new cluster and migration may be needed.

[S38] [S31]

Worked cost calculation verified

Published EKS cluster-support charges are $0.10 per cluster-hour for standard support and $0.60 for extended support. For an illustrative 730-hour month: $73 or $438 for this charge alone. EC2 or Fargate compute, Auto Mode charges where applicable, networking, storage, telemetry and optional features are additional. These are not an estimate for a complete production environment.

[S23]

Decision and pitfall synthesis

Use a tested in-place upgrade when its compatibility and recovery constraints fit. Evaluate blue/green clusters when traffic migration and duplicated infrastructure are worth the additional cost. Neither approach automatically reverses a destructive database migration. Keep application and data rollback plans separate from control-plane recovery.

[S22] [S38]

Further improvement synthesis

Maintain an upgrade calendar and a cost allocation map. Track useful cost per completed business transaction alongside reliability metrics. Evaluate NAT, data transfer and telemetry retention rather than assuming worker instance price is the entire bill. Revisit region and account-specific pricing before a purchase decision.

[S23] [S22]

Keep this: Budget compatibility work and recovery before the support calendar makes the decision for you.

Check yourself: Does reverting a cluster version revert a changed database schema?

No. Version rollback changes eligible control-plane components, not application data migrations. Database compatibility and recovery need an independent plan.