TalosMigrate
Convert OpenShift resources into Rancher/RKE2-ready manifests — preview first, then apply under your control.
TalosMigrate automates the manual conversion work in an OpenShift-to-Rancher/RKE2 migration. It converts OpenShift-specific constructs such as Route, SCC, EgressIP, EgressFirewall, Project and DeploymentConfig into target equivalents like Ingress, Kyverno ClusterPolicy, Cilium policies, Namespace + quota + Pod Security labels and Deployment; it cleans standard resources and rewrites image references for the new registry. It can read resources from a live cluster or from exported YAML files. Preview is the default mode; manifests are written to disk only with explicit confirmation, and applying them to the cluster stays under your control via kubectl or GitOps. Operator inventory, image-mirror and Velero PV-migration scripts, schema validation, a source-to-target cluster diff and health checks live in the same tool. A failing resource does not stop the others from converting. Conversions are deterministic: the same input produces the same manifests.
Modules and capabilities
OpenShift-specific resource conversion
Route → Ingress (TLS via cert-manager), SCC → Kyverno ClusterPolicy, EgressIP/EgressFirewall → Cilium policies, Project → Namespace + quota + PSA, DeploymentConfig → Deployment; storage-class mapping for PVCs, RBAC resources, and Tekton guidance for BuildConfig.
Preview first, apply later
Dry-run is the default; manifests are written to disk only with --apply --confirm. Applying to the cluster stays with you via kubectl or GitOps.
End-to-end toolset
8 CLI commands: conversion, report, schema validation (kubeconform), operator inventory, image-mirror script, Velero script, cluster diff and health check.
Operator migration guidance
Helm equivalents, install commands and CRD migration steps for 10 common operators.
Failure-tolerant batch processing
A resource that cannot be converted is reported as an error while the rest continue; the image-mirror script does not stop on a failed image.
Post-migration verification
Compares source and target clusters per namespace and reports missing, extra and mismatched resources; checks pod readiness and ingress HTTP responses.
How TalosMigrate goes about it
Side by side with the common way of doing the same job; you decide which suits you.
| Capability | TalosMigrate | Common approach |
|---|---|---|
| Conversion | Converts OpenShift-specific resources to target equivalents | Backup/restore tools move resources as they are; platform-specific adaptation is done separately |
| Repeatability | Same input, same output; conversions are idempotent | Usually done with project-specific scripts |
| Verification | Cluster diff + pod and ingress health checks | Usually done with separate tools or by hand |
Modern, production-grade stack
Who this is for
- Platform and infrastructure engineers
- DevOps / platform managers
- SRE and security teams
- Decision-makers evaluating a move from OpenShift to Rancher/RKE2
Plans that fit your scale
For detailed pricing and custom offers, contact our sales team.
Assessment
Inventory, scope and ROI
- Resource inventory and compatibility analysis
- Risk and downtime assessment
- Sample-scenario ROI estimate
- Migration roadmap
Enterprise Program
End-to-end large-scale migration
- Auto-conversion of 20 resource types
- Operator migration guidance
- Diff analysis + health checks
Managed Migration
Run together with the Talos team
- Migration carried out together with the Talos team
- Air-gap / closed-network support
- Cutover plan and rehearsal
- Support scope agreed with you
Is TalosMigrate the right fit for you?
Evaluate the product with a live demo or a pilot set up for your scenario.
Request a demo for TalosMigrate
Fill in the form and our team will contact you to plan a live demo or pilot of TalosMigrate.