القائمة
Check everything that can be upgraded for maintenance across an AWS EKS Kubernetes cluster and output a decision file with Jira-formatted tickets for any required upgrades.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | maintenance-check-aws-eks |
| description | Check everything that can be upgraded for maintenance across an AWS EKS Kubernetes cluster and output a decision file with Jira-formatted tickets for any required upgrades. |
Run this skill when asked to check for available upgrades across an AWS EKS Kubernetes cluster for maintenance. It gathers current versions, compares them against latest available versions, and writes a decision file with Jira-formatted tickets for any required maintenance upgrades.
Update the table below with your cluster names, AWS profiles, and region before using this skill:
<your-aws-region> (e.g. us-east-1, eu-west-1)| Environment | Cluster Name | AWS Profile |
|---|---|---|
| Staging / Non-Prod | <your-staging-cluster> | <your-nonprod-profile> |
| Production | <your-prod-cluster> | <your-prod-profile> |
If the user does not specify an environment, ask before proceeding.
aws eks describe-cluster \
--name <cluster-name> \
--profile <profile> \
--region <your-aws-region> \
--query "cluster.version" \
--output text
Record: current cluster version (e.g. 1.29).
aws eks describe-addon-versions \
--profile <profile> \
--region <your-aws-region> \
--query "sort_by(addons[?addonName=='vpc-cni'].addonVersions[].compatibilities[].clusterVersion, &@) | [-1]" \
--output text
Record: latest available EKS version.
Decision point: If current version == latest version, no maintenance upgrade is needed at all — skip Steps 3–4 and proceed to Step 5 with a "no maintenance upgrade required" output.
List installed add-ons and their current vs. latest versions compatible with the target cluster version:
# List installed add-ons
aws eks list-addons \
--cluster-name <cluster-name> \
--profile <profile> \
--region <your-aws-region> \
--output json
# Current version of each add-on
aws eks describe-addon \
--cluster-name <cluster-name> \
--addon-name <addon-name> \
--profile <profile> \
--region <your-aws-region> \
--query "addon.addonVersion" \
--output text
# Latest version compatible with the target cluster version
aws eks describe-addon-versions \
--addon-name <addon-name> \
--kubernetes-version <target-version> \
--profile <profile> \
--region <your-aws-region> \
--query "addons[0].addonVersions[0].addonVersion" \
--output text
Record for each add-on: name, current version, latest compatible version.
# List node groups
aws eks list-nodegroups \
--cluster-name <cluster-name> \
--profile <profile> \
--region <your-aws-region> \
--output json
# Current AMI release version per node group
aws eks describe-nodegroup \
--cluster-name <cluster-name> \
--nodegroup-name <nodegroup-name> \
--profile <profile> \
--region <your-aws-region> \
--query "{releaseVersion: nodegroup.releaseVersion, version: nodegroup.version}" \
--output json
To find the latest AMI for the target version, take the current AMI name, replace the EKS version with the target version followed by a -*:
aws ec2 describe-images \
--owners amazon \
--filters "Name=name,Values=<ami-name-prefix>-<target-version>-*" \
--profile <profile> \
--region <your-aws-region> \
--query "sort_by(Images, &CreationDate)[-1].{ImageId: ImageId, Name: Name}" \
--output json
For example, if the current AMI name is amazon-eks-node-al2023-x86_64-standard-1.34-v20260107, the filter value becomes amazon-eks-node-al2023-x86_64-standard-1.35-*.
Record for each node group: name, current AMI release version, latest AMI release version.
Write all findings to a Markdown file at:
./maintenance-checks/maintenance-check-aws-eks-<environment>-<YYYY-MM-DD>.md
in the current working directory (the project root).
# Maintenance Upgrade Check — <environment> — <YYYY-MM-DD>
## Decision
**Maintenance upgrade required: Yes / No**
<If no maintenance upgrade required>
The EKS cluster is already on the latest Kubernetes version. No maintenance upgrade is needed.
</If no maintenance upgrade required>
---
## Summary
| Component | Current | Latest |
|---|---|---|
| EKS Cluster (<cluster-name>) | <current> | <latest> |
| EKS Add-on: <addon-name> | <current> | <latest compatible with target> |
| Node Group: <nodegroup-name> AMI | <current> | <latest> |
---
<If maintenance upgrade required>
---
## Jira Ticket
**Title:** Upgrade EKS cluster <cluster-name> from <current> to <target>
**Parent:** `<your-jira-parent-ticket>`
**Label:** `<your-jira-label>`
**Story Points:** `<your-story-points>`
**Refined:** Yes
**Description:**
The EKS cluster `<cluster-name>` is currently running Kubernetes `<current>`.
AWS has released `<target>` as the next supported minor version.
The following work is required:
**1. EKS Control Plane**
- Upgrade EKS control plane from `<current>` to `<target>`
- Verify cluster health post-upgrade
**2. EKS Add-ons**
| Add-on | Current Version | Target Version |
|---|---|---|
| <addon-name> | <current> | <latest compatible with target> |
- Update each add-on above to its latest version compatible with `<target>`
- Verify add-on health post-update
**3. Node Group AMIs**
| Node Group | Current AMI Release | Latest AMI Release |
|---|---|---|
| <nodegroup-name> | <current> | <latest> |
- Update each node group to use the latest AMI release for EKS `<target>`
- Perform rolling node replacement and verify workload health
**References:**
- AWS EKS version lifecycle: https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html
</If maintenance upgrade required>
--region and the correct --profile for the target environment (see table above). Never omit them.update-cluster, update-addon, update-nodegroup, etc.) — this skill is read-only. A human must execute the actual maintenance upgrades.Use the correct AWS CLI profile when running AWS commands based on the target environment.
Analyze code changes between two local Git branches and perform a comprehensive code review. Use ONLY for local git branch comparisons. Do NOT use when a GitLab or GitHub MR/PR URL or MR ID is provided — use gitlab-cli or github-cli skill instead.
Analyze code changes to prepare conventional commit message and commit to a new branch.
Create optimized, secure, production-ready Dockerfiles based on user requirements and application context.
Create a new SKILL.md file based on a guided conversation about a task or workflow.
Create a detailed upgrade plan for a Helm release managed by Terraform, comparing the current and desired chart versions including breaking changes and required code changes.