full-gap-analysis

Identify policy and feature gate differences between OpenShift versions using Python scripts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires oc, jq, python3, PyYAML, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies and reports differences in IAM permissions and feature gates between OpenShift versions, ensuring cloud policy compliance before upgrades.

Core Features & Use Cases

  • Comprehensive Analysis: Covers AWS STS, GCP WIF, feature gates, and OCP admin gate acknowledgments.
  • Version Upgrade Assessment: Validates upgrade readiness for managed OpenShift environments.
  • CI/CD Integration: Designed for use in continuous integration/continuous deployment pipelines.

Quick Start

Run the full-gap-analysis skill to automatically detect and compare the latest stable and candidate versions of OpenShift.

Frequently Asked Questions about full-gap-analysis

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

FAQPage Schema
How do I check OpenShift feature gate and IAM policy differences before a version upgrade?

To check OpenShift feature gate and IAM policy differences before a version upgrade, you need a comprehensive gap analysis. This process compares policy configurations and feature gates between OpenShift versions to ensure cloud compliance and validate upgrade readiness.

What is OpenShift version gap analysis for cloud compliance?

OpenShift version gap analysis is a pre-upgrade compliance check that identifies differences in IAM permissions and feature gates between versions. It ensures environments remain compliant by validating configurations across AWS STS, GCP WIF, and OCP admin gates.

Do I need python3 and oc CLI to validate OpenShift upgrade readiness?

Yes, you need python3, the oc CLI, jq, and PyYAML to validate OpenShift upgrade readiness. These dependencies are required to execute the Python scripts that detect and compare policy differences between stable and candidate versions.

Can I integrate OpenShift feature gate validation into a CI/CD pipeline?

Yes, you can integrate OpenShift feature gate validation into a CI/CD pipeline. The gap analysis process is specifically designed for continuous integration and deployment workflows to automatically detect and compare stable and candidate OpenShift versions.

How does an OpenShift gap analysis handle AWS STS and GCP WIF permissions?

An OpenShift gap analysis handles AWS STS and GCP WIF permissions by detecting and reporting differences in IAM configurations across versions. This comprehensive comparison ensures cloud policy compliance for managed OpenShift environments before upgrades.

What are the limitations of using Python scripts for OpenShift feature gate analysis?

Python scripts for OpenShift feature gate analysis are limited to detecting and comparing configurations between versions. They require specific dependencies including oc, jq, python3, and PyYAML, and are intended solely for pre-upgrade compliance checks in managed environments.