new-migrating-virtual-machines-cli.adoc

Procedure

1. Create a Secret manifest for the source provider credentials:

2. Create a Provider manifest for the source provider:

3. Optional: Create a Hook manifest to run custom code on a VM during the phase specified in the Plan CR:

   $  cat << EOF | {oc} apply -f -
   apiVersion: forklift.konveyor.io/v1beta1
   kind: Hook
   metadata:
     name: <hook>
     namespace: <namespace>
   spec:
     image: quay.io/konveyor/hook-runner
     serviceAccount:<service account> (1)
     playbook: |
       LS0tCi0gbm... (2)
   EOF

   1. (Optional) {ocp} service account. The serviceAccount must be provided if you want to manipulate any resources of the cluster.

   2. Base64-encoded Ansible Playbook. If you specify a playbook, the image must include an ansible-runner.

      Note	You can use the default hook-runner image or specify a custom image. If you specify a custom image, you do not have to specify a playbook.

4. Create a Migration manifest to run the Plan CR:

   $ cat << EOF | {oc} apply -f -
   apiVersion: forklift.konveyor.io/v1beta1
   kind: Migration
   metadata:
     name: <name_of_migration_cr>
     namespace: <namespace>
   spec:
     plan:
       name: <name_of_plan_cr>
       namespace: <namespace>
     cutover: <optional_cutover_time>
   EOF

   Note	If you specify a cutover time, use the ISO 8601 format with the UTC time offset, for example, 2024-04-04T01:23:45.678+09:00.