| 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*) |
RHDH EKS Test Management
List EKS test entries and update the K8s version used by EKS MAPT clusters.
When to Use
- List which EKS test entries exist per RHDH release branch
- Check which K8s version each branch is configured to use
- Update the EKS K8s version after a lifecycle check
- The version is set per branch via
MAPT_KUBERNETES_VERSION in each CI config file
Prerequisites
yq (v4+) for listing tests
Listing Tests
bash "${CLAUDE_SKILL_DIR}/scripts/list-k8s-test-configs.sh" \
--pattern "^e2e-eks-"
Filter by branch: add --branch main.
Updating the Version
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.
Related Skills
rhdh-eks-lifecycle: Check which K8s versions are supported before updating
