eksup
eksup copied to clipboard
clowdhaus
Feature request: Allow users to specify the target version (e.g. n+3)
Use case
EKS now support customers to upgrade the control plane to n+3 consequently, and then upgrade their data plane in one go. But eksup can only support n+1.
Solution/User Experience
Allow users to specify the target version and produce the report for the target version. For example:
# Add target-version parameter
eksup create playbook --cluster <> --region <> --target-version 1.31
# Sample output
┌────────┬────┬────────────────────────┬────────────────────┬─────────────────────┬─────────────────────┐
│ CHECK │ │ NAME │ CURRENT │ LATEST │ DEFAULT │
├────────┼────┼────────────────────────┼────────────────────┼─────────────────────┼─────────────────────┤
│ EKS005 │ ❌ │ adot │ v0.94.1-eksbuild.1 │ v0.109.0-eksbuild.2 │ v0.109.0-eksbuild.2 │
│ EKS005 │ ⚠️ │ aws-ebs-csi-driver │ v1.29.1-eksbuild.1 │ v1.37.0-eksbuild.1 │ v1.37.0-eksbuild.1 │
│ EKS005 │ ⚠️ │ aws-efs-csi-driver │ v2.0.5-eksbuild.1 │ v2.1.0-eksbuild.1 │ v2.1.0-eksbuild.1 │
│ EKS005 │ ❌ │ coredns │ v1.11.1-eksbuild.6 │ v1.11.3-eksbuild.2 │ v1.11.3-eksbuild.1 │
│ EKS005 │ ⚠️ │ eks-pod-identity-agent │ v1.2.0-eksbuild.1 │ v1.3.4-eksbuild.1 │ v1.3.4-eksbuild.1 │
│ EKS005 │ ❌ │ kube-proxy │ v1.29.3-eksbuild.2 │ v1.31.2-eksbuild.3 │ v1.31.2-eksbuild.3 │
│ EKS005 │ ❌ │ vpc-cni │ v1.15.5-eksbuild.1 │ v1.19.0-eksbuild.1 │ v1.19.0-eksbuild.1 │
└────────┴────┴────────────────────────┴────────────────────┴─────────────────────┴─────────────────────┘
Alternative solutions
No response
