Topic lessonTopic: Kubernetes and EKS: structure, networking and upgrades
EKS upgrades and recovery: support deadlines, nodes and workloads
An EKS control-plane upgrade does not establish that nodes, add-ons and applications all upgraded together. Identify each change, then align support deadlines, compatibility, availability during the change and recovery conditions. An update status alone does not prove successful user operations.
Separate update targets and ownership; explain standard/extended support, PDB boundaries, conditional rollback and data recovery.
The control plane coordinates Kubernetes; nodes run Pods. An AMI is a machine image, kubelet manages Pods on a node, and add-ons provide capabilities such as DNS/networking. No live account is required.
Separate the target and owner of each update
| Target | Example change | Separate verification |
|---|---|---|
| Application | Deployment Pod template or image. | Readiness, user responses and data compatibility. |
| Control plane | Kubernetes minor version. | Node/add-on/client compatibility and observed versions. |
| Node | AMI, kubelet or execution infrastructure. | Eviction destinations, placement, startup and readiness. |
| Add-on | VPC CNI, CoreDNS and related components. | Supported versions, configuration, dependencies and behavior. |
- Control plane → Nodes / kubeletCompare compatibility and actual versions
- Control plane → Add-ons / clientsReview supported combinations
- Nodes / kubelet → Application / dataObserve placement and execution
- Control plane
- Kubernetes control-plane version
- Nodes / kubelet
- Check updates for the compute approach
- Add-ons / clients
- Check compatible versions and settings
- Application / data
- Verify user operations
Record current version, target, owner, verification method and stop conditions for each layer. An application Pod-template change and a Kubernetes cluster-version change are distinct operations.
Separate support durations from the actual deadline
| Phase | Documented duration/condition | Planning implication |
|---|---|---|
| Standard support | 14 months from EKS availability. | Do not substitute the upstream Kubernetes release date. |
| Extended support | 12 months after standard support; additional cluster-hour charges. | Review upgrade policy and costs. |
| After extended support | Control plane becomes subject to automatic upgrade. | Plan proactively rather than relying on an exact automatic-update time. |
Knowing the duration does not establish a particular cluster’s deadline. Match its version and upgrade policy to the official support calendar. Calendar dates use UTC; month-only dates are approximate. References were checked on 2026-10-26; no version is labelled permanently latest.
Distinguish EXTENDED from a policy that avoids extension and triggers automatic upgrading at standard-support end. Managed/self-managed nodes and existing Fargate Pods still need separate version checks. Review compute, storage, networking and optional features as well as support charges.
Check compatibility and advance one minor version at a time
EKS control-plane minor upgrades proceed one step at a time. Review deprecated APIs, cluster insights and node/add-on/kubectl compatibility first. Allowed version skew does not authorize arbitrary combinations or sequencing.
| Approach | Update verification |
|---|---|
| Managed node group | Plan node updates separately; observe versions and Pods afterwards. |
| Self-managed nodes | Customer-managed node versions, maintenance and compatibility. |
| Auto Mode | Inspect AWS-managed update behavior and workload disruption/outcomes. |
| Fargate | Do not assume existing Pod kubelets updated; plan replacement and validation. |
For application rollout, match Deployment configuration with old/new Pod observations and actual user operations. Do not reuse ECS minimumHealthyPercent/maximumPercent as Kubernetes settings. Similar terminology does not make the rules identical.
Distinguish disruptions constrained by a PDB
A PodDisruptionBudget (PDB) constrains unavailable replicas during supported voluntary eviction. Draining a node evicts workloads for relocation. A PDB does not block every direct deletion, node failure or workload-controller rollout.
| Operation | PDB behavior | Decision evidence |
|---|---|---|
| Rolling update | Respects PDBs; inability to drain can fail the update. | Check readiness, spare resources and placement constraints. |
| Force update | Does not respect PDBs. | Do not treat ignored disruption constraints as a routine shortcut. |
| Scaling down desiredSize | Not protected like the ordinary update/drain workflow. | Plan node termination and application effects separately. |
Seven days is only one control-plane rollback condition
EKS documentation checked on 2026-10-26 describes rollback to the previous minor version within seven days of an in-place upgrade completing. A cluster created at its current version is ineligible. Support/policy, cluster state, incompatible features, readiness insights and node/add-on compatibility also matter.
| Record | What is established | What remains unknown |
|---|---|---|
| 48 hours since completion; previous minor proposed. | Within the time window. | Whether other eligibility conditions hold. |
| 192 hours since completion. | Exceeds seven days: 168 hours. | Feasibility and conditions of other recovery approaches. |
Auto Mode nodes are managed within rollback; managed node groups and other compute need separate preparation. Do not assume equivalent Fargate-node rollback. Control-plane rollback preserves customer data/workloads and does not revert add-ons. Force is not a universal override of prerequisites such as the time window.
Define recovery targets and post-recovery verification
- Stop further changes and align targets, versions, times and user impact.
- Identify application, node, control-plane and add-on recovery separately.
- Check deadlines, support, insights, data compatibility and ownership.
- Assess disruption and persistent writes/external notifications for the chosen approach.
- Verify actual versions, Pods, connectivity and user operations, not only operation status.
Check update targets and recovery conditions
Choose an option to see the result and explanation.
Check, then explain in your own words
- Identify four update targets and their owners.
- Separate support duration from actual version/policy/deadline.
- Explain PDB and rollback boundaries, then define post-recovery observations.
Check your understanding: A report says only “cluster upgrade successful.” What would you verify next?
The changed target/version, support deadline, node/add-on/client compatibility and actual versions, Pod/connectivity/user outcomes, rollback conditions and data state.
One operation’s success does not establish synchronized component updates or application/data recovery.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
Scope and conditionsSeparate control plane, nodes, add-ons and clients; minor upgrade sequencing depends on current compatibility rules. Documentation review; not live-cluster verification.
Used in this lessonSeparate the target and owner of each update Check compatibility and advance one minor version at a time Check update targets and recovery conditions
- Kubernetes: DeploymentsChecked:
Scope and conditionsPod-template updates and desired state; do not import ECS percentage formulas into Kubernetes. Documentation review; not live-cluster verification.
Used in this lessonSeparate the target and owner of each update Check compatibility and advance one minor version at a time
Scope and conditionsReview standard/extended support timing and upgrade policy separately from exact version eligibility; not a live-cluster check.
Used in this lessonSeparate support durations from the actual deadline Check compatibility and advance one minor version at a time
- Amazon EKS pricingChecked:
Scope and conditionsSeparate cluster support, compute and additional feature charges; no price or free-use guarantee from Pod count.
Used in this lessonSeparate support durations from the actual deadline
Scope and conditionsManaged-node update is separate; rolling respects PDB while force does not. Node version cannot exceed control plane. Documentation review; not live-cluster verification.
Used in this lessonCheck compatibility and advance one minor version at a time Distinguish disruptions constrained by a PDB
- Kubernetes: DisruptionsChecked:
Scope and conditionsPDB does not prevent every disruption or direct deletion; distinguish eviction from deletion. Documentation review; not live-cluster verification.
Used in this lessonDistinguish disruptions constrained by a PDB Check update targets and recovery conditions
Scope and conditionsConditional previous-minor rollback within seven days of in-place upgrade; not data, workload or add-on undo. Documentation review; not live-cluster verification.
Used in this lessonSeven days is only one control-plane rollback condition Check update targets and recovery conditions