create-cpo-override

Creates control-plane-operator image override entries in overrides.yaml with verified PR fixes.

538|560|Updated Jan 18, 2021
One-click install
npx skills add https://github.com/openshift/hypershift --skill create-cpo-override
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-cpo-override
Source: https://github.com/openshift/hypershift/tree/main/.claude/skills/create-cpo-override
Command: npx skills add https://github.com/openshift/hypershift --skill create-cpo-override

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating CPO image overrides for HyperShift requires resolving the right container images, verifying that required PR fixes are actually present in those images, checking z-stream development cutoff dates to avoid upgrade regressions, and editing overrides.yaml in the exact expected format — a slow, error-prone process.

Core Features & Use Cases

  • Automated image resolution: Searches stable payloads, fast payloads, and Konflux push builds in order to find an image containing all required PRs, verified via git merge-base ancestry checks.
  • Regression-safe version ranges: Resolves z-stream ranges from the Cincinnati upgrade graph API and checks development cutoff dates against PR merge dates so customers do not regress when upgrading past the override range.
  • End-to-end PR preparation: Edits overrides.yaml following existing conventions, runs unit tests, and generates a commit message and PR description with validation contract lines compatible with the validate-pr-override-images workflow.
  • Use Case: A Jira ticket requires CPO fixes on AWS and Azure for OCP 4.20 and 4.21; the skill resolves Konflux images, verifies the PRs are included, writes the override entries, and prepares a validated PR.

Quick Start

Ask the assistant to create a CPO override for a given Jira ticket, platforms, branches, and required PR numbers, then confirm the generated summary before it edits overrides.yaml.

Frequently Asked Questions about create-cpo-override

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

FAQPage Schema
How do I create a CPO image override in HyperShift?

Provide the platforms, Jira ticket, OCP branches, version ranges, and required PR numbers. The workflow resolves a suitable image from stable payloads, fast payloads, or Konflux push builds, verifies the PRs are included, and edits overrides.yaml.

How are override images verified to contain required PRs?

Verification uses skopeo inspect to read the image's vcs-ref label, gh pr view to get the PR merge commit, and git merge-base --is-ancestor to confirm the fix is in the image's commit history.

What tools are required to create CPO overrides?

You need skopeo and oc installed for image inspection, an authenticated gh CLI, a local git repo with release branches fetched, and internet access to quay.io and the Cincinnati API. A pull secret may be required for payload images.

Why does the override range check development cutoff dates?

If a customer upgrades from an overridden version to the next z-stream that lacks the fix, they regress. Comparing PR merge dates against the next z-stream's development cutoff determines whether the override range must be extended.

What happens if no image contains all required PRs?

The workflow reports which sources were tried, points to the build-cpo-image dev skill and the Konflux hotfix process in contrib/konflux/README.md, and asks you to provide an image reference manually for verification.