Topic lessonTopic: Applied container, data, cost and AI labs
Model an EKS upgrade window|Version support and compatibility
EKS minor versions have standard and extended support phases. Upgrade timing must also account for removed APIs and add-on compatibility.
Compare API compatibility and the support lifecycle at a proposed change date.
The cases use fictional inputs.
What to predict
EKS minor versions have standard and extended support phases. Upgrade timing must also account for removed APIs and add-on compatibility.
- Months since release → Months until maintenanceAlign conditions
- Months until maintenance → API compatibilityCompare outcomes
- API compatibility → DecisionVerify the decision
- Months since release
- 8 / 13
- Months until maintenance
- 2 / 4
- API compatibility
- Verified / Removed API identified
- Decision
- Compare API compatibility and the support lifecycle at a proposed change date.
Compare the cases
| Case | Conditions | Decision |
|---|---|---|
| Trial 1 | Months since release 8, Months until maintenance 2, API compatibility Verified | The proposed window is within standard support. Verify workloads in a test cluster. |
| Trial 2 | Months since release 13, Months until maintenance 2, API compatibility Verified | The proposed window falls during extended support. Review costs and upgrade conditions. |
| Trial 3 | Months since release 25, Months until maintenance 2, API compatibility Verified | The model reaches the end of extended support. Verify calendar dates and the upgrade plan. |
| Trial 4 | Months since release 8, Months until maintenance 2, API compatibility Removed API identified | Hold for compatibility. Test replacement for the removed API. |
Acceptance and limits
Models synthetic month counts at 14 and 26 months. Check actual dates, upgrade policy and prices in official references.
Read the initial conditions and operational goal.
Change one condition and compare the decision.
Record the model boundary and outstanding checks.
Change a condition
Models synthetic month counts at 14 and 26 months. Check actual dates, upgrade policy and prices in official references.
The proposed window is within standard support. Verify workloads in a test cluster.
{"api":"Hold for compatibility. Test replacement for the removed API.","end":"The model reaches the end of extended support. Verify calendar dates and the upgrade plan.","extended":"The proposed window falls during extended support. Review costs and upgrade conditions.","standard":"The proposed window is within standard support. Verify workloads in a test cluster."}Check your understanding
Choose an option to see the result and explanation.
Check, then explain in your own words
- Read the initial conditions and operational goal.
- Change one condition and compare the decision.
- Record the model boundary and outstanding checks.
Check your understanding: Compare API compatibility and the support lifecycle at a proposed change date.
Models synthetic month counts at 14 and 26 months. Check actual dates, upgrade policy and prices in official references.
Record the model boundary and outstanding checks.
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 conditionsEKS minor versions have standard and extended support phases. Upgrade timing must also account for removed APIs and add-on compatibility.
Used in this lessonWhat to predict Acceptance and limits