# Openshift Upgrade

> Assess OpenShift cluster update readiness, supported version paths, API removals, Operators, MachineConfigPools, disruption budgets and disconnected release availability. Use to plan or accompany an explicitly requested cluster update and verify completion. Use openshift-disconnected for building image mirrors.

- Skill: `msilich/openshift-upgrade` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds@latest add msilich/openshift-upgrade`
- Raw SKILL.md: https://api.skillmd.com/api/skills/msilich/openshift-upgrade/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: msilich (https://skillmd.com/u/msilich)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/msilich/openshift-upgrade

---


# OpenShift update readiness and execution

Assess the requested current-to-target update with evidence, then accompany execution only when explicitly requested.

## Start here

1. Read [the shared domain contract](../openshift-mcp/references/domain-contract.md).
2. Read [the source map](references/sources.md) and the local sections relevant to this task.
3. Use [readiness.md](references/readiness.md) before an update. Use [execution.md](references/execution.md) for an approved update or a stalled update.
4. Use [openshift-api](../openshift-api/SKILL.md) to verify schemas and [openshift-mcp](../openshift-mcp/SKILL.md) to perform permitted operations.

This skill depends on the other nine skills being installed as sibling directories.
Resolve every path from this file. Missing documentation, a version mismatch, a
denied access or an unknown schema must remain explicit; do not silently proceed
with a substitute. Pure document lookup belongs to [openshift-docs](../openshift-docs/SKILL.md).

## Report

State the evidence-backed result, target and observed versions, local source path
and section, changes actually performed, verification, and any remaining unknowns.