// Analyze RHDH OCP version coverage by cross-referencing cluster pools and CI test configs against both RHDH and OCP lifecycle APIs to find gaps, stale configurations, and compatibility mismatches
| name | rhdh-ocp-coverage |
| description | Analyze RHDH OCP version coverage by cross-referencing cluster pools and CI test configs against both RHDH and OCP lifecycle APIs to find gaps, stale configurations, and compatibility mismatches |
| allowed-tools | Read, Bash(bash *analyze-coverage.sh*) |
Cross-reference RHDH cluster pools, CI test configurations, RHDH lifecycle data, and OCP lifecycle data to identify coverage gaps and stale configurations.
Use this skill when you need to:
curl, jq, and yq (v4+) must be availablehttps://access.redhat.comopenshift/release repositoryCLAUDE_SKILL_DIR is set automatically by the Claude Code skill loader. For manual invocation, set it to this skill's directory (e.g., CLAUDE_SKILL_DIR=ci-operator/config/redhat-developer/rhdh/.claude/skills/rhdh-ocp-coverage)Run the bundled analysis script from the repository root:
bash "${CLAUDE_SKILL_DIR}/scripts/analyze-coverage.sh"
The analysis checks two independent dimensions for each OCP version:
| Dimension | Source | Meaning |
|---|---|---|
| OCP supported | OCP lifecycle API | The OCP version itself is still receiving updates (Full, Maintenance, or EUS) |
| RHDH supported | RHDH lifecycle API (openshift_compatibility field) | RHDH officially supports running on this OCP version |
An OCP version must satisfy both to warrant a cluster pool and test entry:
main Branch Is HandledThe main branch targets the next unreleased RHDH version. Since it's unreleased, it doesn't appear in the RHDH lifecycle API. The script estimates its OCP support as:
Latest active RHDH release's OCP versions + any newer OCP versions that have reached GA
For example, if RHDH 1.9 supports OCP 4.16-4.21 and OCP 4.22 just went GA, then main is estimated to support 4.16-4.22.
A combined view showing each relevant OCP version with:
| Column | Description |
|---|---|
| OCP | Version number |
| OCP_SUPP | Is OCP itself still supported? |
| RHDH_SUPP | Does any active RHDH release support this OCP? |
| OCP_PHASE | Current OCP lifecycle phase |
| RHDH_RELEASES | Which RHDH releases support this OCP |
Actions are categorized by severity:
Specific checks:
Counts per action category plus the per-branch OCP support mapping.
After running the analysis:
rhdh-ocp-pool and rhdh-ocp-tests skillsmake update after all changeshttps://access.redhat.com/product-life-cycles/api/v1/products?name=Red+Hat+Developer+Hubhttps://access.redhat.com/product-life-cycles/api/v1/products?name=OpenShift+Container+Platform+4https://access.redhat.com/support/policy/updates/developerhubrhdh-ocp-lifecycle — Check RHDH and OCP version support statusrhdh-ocp-pool — List and generate OCP cluster pool configurationsrhdh-ocp-tests — List, generate, add, and remove OCP test entriesCheck 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.
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.
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.