msilich OpenShift Dev Spaces
Use local product documentation to investigate the platform or a named developer workspace. A running pod alone does not demonstrate that a workspace or IDE works.
Start here
- Read the shared domain contract.
- Read the source map, then the relevant local chapters.
- Select administration for installation, CheCluster configuration and upgrades; workspaces for devfiles, storage and lifecycle; airgap for mirrors, dependencies and extensions; troubleshooting for failures.
- For cluster operations load openshift-mcp; verify served resources and fields with openshift-api.
Install all ten skills as sibling directories. Resolve paths from this file. Use openshift-docs for pure document lookup. Documentation 3.29 does not establish compatibility with either bundled OCP version: compare the installed Dev Spaces, Dev Workspace Operator and OCP versions with local support evidence. Report missing compatibility information rather than assuming support.
Diagnosis is read-only. Follow the existing Day-2 approval workflow only for an
explicitly requested change. Do not invent Dev Spaces MCP tools, auto-install dsc,
switch identity, or choose a Secret policy for the user. A missing local source or
unknown schema stops that version-specific procedure; denied access is not an
invitation to retry through oc.
Report
State the target workspace/platform, observed versions, local document path and section, observed facts and remaining uncertainty. For changes report the actual delta and verification, including the user's original workspace or IDE symptom.