You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ Crane is composed of several repositories:
26
26
*[backube/pvc-transfer](https://github.com/backube/pvc-transfer): The library that powers the Persistent Volume migration ability, shared with the [VolSync](https://volsync.readthedocs.io/en/stable/index.html) project. State migration of Persistent Volumes is handled by rsync allowing storage migrations between different storage classes.
27
27
*[migtools/crane-runner](https://github.com/migtools/crane-runner): A collection of resources showing how to leverage Tekton to build migration workflows with Crane
28
28
*[migtools/crane-ui-plugin](https://github.com/migtools/crane-ui-plugin): A dynamic UI plugin for the [openshift/console](https://github.com/openshift/console)
29
-
*[migtools/mtrho-operator](https://github.com/migtools/mtrho-operator): An Operator which deploys Crane in an opinionated manner leveraging Tekton for migrating applications
29
+
*[migtools/crane-operator](https://github.com/migtools/crane-operator): An Operator which deploys Crane in an opinionated manner leveraging Tekton for migrating applications
30
30
31
31
How does it work? Crane works by:
32
32
1) Inspecting a running application and exporting all associated resources
0 commit comments