AWS eks documentation change
Summary
Added documentation for rollback readiness insights that identify issues impacting Kubernetes version rollbacks after upgrades.
Security assessment
The change adds operational guidance for cluster version management but contains no security-specific content, vulnerability fixes, or security feature documentation.
Diff
diff --git a/eks/latest/userguide/cluster-insights.md b/eks/latest/userguide/cluster-insights.md index 1d340923f..2f0ec58c7 100644 --- a//eks/latest/userguide/cluster-insights.md +++ b//eks/latest/userguide/cluster-insights.md @@ -22,0 +23,2 @@ Amazon EKS cluster insights provide detection of issues and recommendations to r + * **Rollback readiness insights** : Identifies issues that could impact your ability to roll back to a previous Kubernetes version after an upgrade. + @@ -31,0 +34,2 @@ Amazon EKS cluster insights provide detection of issues and recommendations to r + * **Rollback readiness availability** : Rollback readiness insights are only available for clusters that have been upgraded within the last 7 days. After the 7-day rollback eligibility window expires, these insights are no longer generated for the cluster. + @@ -58,0 +63,14 @@ EKS cluster insights automatically scans Amazon EKS clusters with hybrid nodes t +### Rollback readiness insights + +Rollback readiness insights are a specific type of insight checks within cluster insights. These checks return insights related to Kubernetes version rollback readiness. Amazon EKS runs rollback readiness insight checks on clusters that have been upgraded within the last 7 days. Rollback readiness insights are point-in-time checks—they reflect the cluster state at the time of evaluation, not continuously. + +After upgrading your cluster Kubernetes version, you can use the **Upgrade insights** tab of the observability dashboard in the [Amazon EKS console](https://console.aws.amazon.com/eks/home#/clusters) to review rollback readiness insights. If your cluster has identified issues, review them and make appropriate fixes. The issues include links to Amazon EKS and Kubernetes documentation. After fixing the issue, refresh cluster insights on-demand to fetch the latest insights. If all issues have been resolved, you can proceed with the rollback. + +Amazon EKS returns insights related to Kubernetes version rollback readiness under the `ROLLBACK_READINESS` category. Rollback readiness insights identify possible issues that could impact a Kubernetes cluster version rollback. This minimizes the effort that administrators spend preparing for rollbacks and increases the reliability of reverting to a previous version. Clusters are automatically scanned by Amazon EKS against a list of possible rollback-impacting issues, including API usage compatibility (which covers incompatibility checks during API version graduation where a previous API version is removed, new resources that do not exist in the desired version, and new field or enum changes), cluster health, kubelet and kube-proxy version skew, EKS managed add-on compatibility, and for Auto Mode clusters, disruption budget and annotation checks. + +###### Note + +Rollback readiness insights only check EKS-managed add-on versions. For self-managed add-ons, or if you have overridden the version of a managed add-on outside of the EKS add-on lifecycle, insights do not detect version incompatibilities. You are responsible for validating compatibility of those add-ons with the target version before rolling back. + +Insights with ERROR or UNKNOWN status block the rollback until the issue is resolved. You can use the `--force` flag to bypass insight checks if you choose to proceed at your own risk. Insights with WARNING status are advisory and do not prevent rollback. For more information, see [Rollback cluster to previous Kubernetes version](./rollback-cluster.html). +