Migrate a Kubernetes GitOps repository to OpenChoreo. Analyzes K8s resources (raw YAML or Kustomize overlays) and generates a standards-compliant OpenChoreo GitOps structure.
Orchestrates a complete Kubernetes → OpenChoreo migration in three phases:
/k8s-oc-migrate [k8s-repo-path] [output-dir]
$0 = path to K8s GitOps repo (required — use . for current directory)$1 = output directory for OC GitOps files (default: ./openchoreo-gitops/)Invoke the k8s-oc-explore skill with the source path:
/k8s-oc-explore <k8s-repo-path>
The explore skill will:
oc-migration-inventory.jsonWait for the user to confirm the mapping before proceeding.
If the user requests changes to the mapping:
oc-migration-inventory.jsonAfter the inventory is confirmed, invoke the k8s-oc-generate skill:
/k8s-oc-generate oc-migration-inventory.json <output-dir>
The generate skill will:
namespaces/ structurePresent the summary to the user. Point out any warnings that require manual attention.
Ask the user:
"Generation complete! Would you like to apply these files to a running OpenChoreo instance now?
Options:
- Yes, use MCP — I'll use OpenChoreo MCP tools if available
- Yes, use kubectl — apply via
kubectl apply -f <output-dir> --recursive- No, I'll do it manually — review files first and apply later"
If the user chooses to apply:
/k8s-oc-apply <output-dir>
After all phases complete, print:
## Migration Complete
Source: <k8s-repo-path>
Output: <output-dir>
Inventory: oc-migration-inventory.json
### Results
- Projects created: N
- Components migrated: N
- ReleaseBindings generated: N (M environments each)
- Warnings requiring manual review: N
### Manual Review Required
<list any items from warnings that need human attention>
### Files Generated
<output-dir tree>
This skill's reference/ directory contains:
mapping-table.md — complete K8s → OC resource mappingoc-yaml-patterns.md — canonical OC YAML examplesedge-cases.md — enterprise edge case handling guide