openshift/rhdh-aks-lifecycle
>- Check 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.
npx skills add https://github.com/openshift/release --skill rhdh-aks-lifecycle
rhdh-aks-tests to make changes)curl, jq, yq (v4+), internet connectivitybash "${CLAUDE_SKILL_DIR}/scripts/check-aks-lifecycle.sh" \
--mapt-ref ci-operator/step-registry/redhat-developer/rhdh/aks/mapt/create/redhat-developer-rhdh-aks-mapt-create-ref.yaml \
--test-pattern "^e2e-aks-"
The script queries two sources:
https://releases.aks.azure.com/parsed_data.json — official AKS release status with per-region K8s version availability (major.minor only)https://endoflife.date/api/azure-kubernetes-service.json — community-maintained EOL datesWebFetch https://learn.microsoft.com/en-us/azure/aks/supported-kubernetes-versions
The script outputs three sections:
Always update the main branch to the newest GA version. If the configured version on main is not the newest GA version, proceed to update it using the rhdh-aks-tests skill to change MAPT_KUBERNETES_VERSION in the main CI config file.
For release branches (e.g., release-1.9, release-1.8), ask the user whether they should also be updated before making changes.
rhdh-aks-tests: Update the AKS K8s version and list test entriesTake openshift/rhdh-aks-lifecycle from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.