versions-channels-gap

Validate OpenShift version release channels and upgrade paths via the Cincinnati API.

12|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/openshift-online/rosa-gap-analysis --skill versions-channels-gap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: versions-channels-gap
Source: https://github.com/openshift-online/rosa-gap-analysis/tree/main/skills/versions-channels-gap
Command: npx skills add https://github.com/openshift-online/rosa-gap-analysis --skill versions-channels-gap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, and includes scripts (resource) components.

What problem does it solve?

This Skill addresses the need for teams to ensure that target versions of OpenShift are available in the expected release channels and that there are valid upgrade paths, providing a seamless and secure upgrade process.

Core Features & Use Cases

  • Version Channel Validation: Checks the availability of specified versions across release channels.
  • Upgrade Path Verification: Ensures that there are valid upgrade paths between versions.
  • Cross-Source Consistency: Validates consistency across Sippy, accepted streams, and Cincinnati data.

Quick Start

Analyze the available channels for version 4.22: Run the following command: python3 ./scripts/gap-versions-channels.py --version 4.22

Frequently Asked Questions about versions-channels-gap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify OpenShift upgrade paths before planning a cluster upgrade?

OpenShift upgrade paths are verified by checking target version availability across release channels using the Cincinnati API and accepted streams data. This Skill validates channel status, accepted versions, and valid upgrade routes for pre-upgrade planning.

What is OpenShift release channel validation and when do I need it?

OpenShift release channel validation checks whether target versions exist in expected channels and have valid upgrade paths. It is needed during pre-upgrade planning to ensure seamless, secure cluster transitions across available release streams.

How do I check available release channels for a specific OpenShift version?

To check available release channels for a specific OpenShift version, run the validation script with the target version parameter. For example, execute `python3 ./scripts/gap-versions-channels.py --version 4.22` to analyze channel availability.

Can I validate OpenShift version consistency across Sippy, accepted streams, and Cincinnati data?

Yes, OpenShift version consistency can be validated across Sippy, accepted streams, and Cincinnati data. This cross-source consistency checking ensures that version availability and upgrade paths align across all three data sources.

Do I need Python and the requests library to validate OCP version release channels?

Yes, Python and the requests library are required to validate OCP version release channels. The Skill is implemented as Python scripts and depends on the requests library to query the Cincinnati API and accepted streams data.

Why are OpenShift upgrade paths not showing for my target release channel?

OpenShift upgrade paths may not show for a target release channel if the version is not in accepted streams or lacks valid Cincinnati API routes. Cross-source consistency validation helps identify whether the gap is in channel status or version acceptance.