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.