// List EKS test entries in RHDH ci-operator config files and update the EKS Kubernetes version per branch. Use when listing e2e-eks tests, changing MAPT_KUBERNETES_VERSION for EKS, or checking which EKS K8s version each release branch uses.
| name | rhdh-eks-tests |
| description | List EKS test entries in RHDH ci-operator config files and update the EKS Kubernetes version per branch. Use when listing e2e-eks tests, changing MAPT_KUBERNETES_VERSION for EKS, or checking which EKS K8s version each release branch uses. |
| allowed-tools | Read, Edit, Bash(bash *list-k8s-test-configs.sh*) |
List EKS test entries and update the K8s version used by EKS MAPT clusters.
MAPT_KUBERNETES_VERSION in each CI config fileyq (v4+) for listing testsbash "${CLAUDE_SKILL_DIR}/scripts/list-k8s-test-configs.sh" \
--pattern "^e2e-eks-"
Filter by branch: add --branch main.
The K8s version is set per branch as the MAPT_KUBERNETES_VERSION env var in each CI config file:
ci-operator/config/redhat-developer/rhdh/redhat-developer-rhdh-<branch>.yaml
Each EKS test entry has MAPT_KUBERNETES_VERSION under steps.env. Update all EKS test entries in the file — each branch typically has multiple EKS tests that should use the same version. To update, use the Edit tool to change the value for the target branch. Example:
steps:
env:
MAPT_KUBERNETES_VERSION: "1.35"
Verify the MAPT image tag in the ref YAML is compatible with the new K8s version:
ci-operator/step-registry/redhat-developer/rhdh/eks/mapt/create/redhat-developer-rhdh-eks-mapt-create-ref.yaml
NOTE: Each branch can use a different K8s version. make update is NOT required for version changes.
rhdh-eks-lifecycle: Check which K8s versions are supported before updatingCheck AKS Kubernetes version support status using the official AKS release status API and compare against versions configured in CI config files. Use whenever someone asks about AKS K8s version support, EOL dates, deprecation, or whether the configured AKS version is still GA. Also use when planning AKS K8s version upgrades — run this before using rhdh-aks-tests to make changes.
List AKS test entries in RHDH ci-operator config files and update the AKS Kubernetes version per branch. Use when listing e2e-aks tests, changing MAPT_KUBERNETES_VERSION for AKS, or checking which AKS K8s version each release branch uses.
Check EKS Kubernetes version support status using the official AWS EKS docs source and compare against versions configured in CI config files. Use whenever someone asks about EKS K8s version support, EOL dates, or whether the configured EKS version is still in standard support. Also use when planning EKS K8s version upgrades — run this before using rhdh-eks-tests to make changes.
Check GKE Kubernetes version support status using the endoflife.date API (auto-scraped from Google's GKE release schedule). Use whenever someone asks about GKE K8s version support, EOL dates, or whether the current GKE cluster version is still supported. GKE uses a long-running static cluster whose version is not managed in CI config.
List GKE test entries in RHDH ci-operator config files. Use when listing e2e-gke tests or checking which branches have GKE test entries. Unlike AKS/EKS, GKE uses a pre-existing static cluster — version upgrades are performed via the GCP Console.
Use when decommissioning an end-of-life RHDH release branch by removing CI config, generated Prow jobs, and branch protection from the openshift/release repository