eks-upgrade-check

To check for deprecated Kubernetes APIs before an EKS cluster upgrade, use tools like Pluto and Kubent to scan your current manifests. This process identifies removed or deprecated APIs early, allowing you to remediate manifests and generate an actionable upgrade runbook.

Validating EKS addon compatibility during an upgrade involves checking your current addons against the target Kubernetes version. The process performs compatibility validation between versions to ensure addons are supported and produces a pre-upgrade risk assessment report.

An EKS upgrade runbook includes pre-upgrade checks, deprecated API detection, addon compatibility validation, and risk assessment. It provides an actionable upgrade plan and rollback planning to ensure production cluster upgrades are executed safely with minimal disruption.

Yes, you can assess rollback risks before upgrading an EKS environment by generating a pre-upgrade risk assessment. This involves validating compatibility between your current and target Kubernetes versions and creating a structured rollback plan as part of your runbook.

Yes, EKS upgrade planning requires checking compatibility between your current and target Kubernetes versions. This validation ensures your manifests and addons are fully supported by the target version, preventing compatibility issues during the cluster upgrade process.

Deprecated API detection tools matter for Kubernetes upgrade planning because they identify APIs that have been removed in the target version. Detecting these compatibility issues early prevents upgrade failures and ensures your manifests are updated before execution.