Sample playbook showing the workflow for performing GVK conversion to finish a mig-controller migration when GVK incompatibilities were detected.
| Steps |
|---|
| 1. Run a migration with mig-controller |
| 2. Take note of the MigPlan name used, as well as the S3 bucket name |
2. Supply values for the ansible vars migplan_name and bucket_name by editing playbook.yml or using ansible extra vars |
3. Ensure you have a new enough oc client version to perform the conversion (should match newer cluster involved in migration) |
| 4. Run the playbook |
Converted files will be dropped in a new directory convert_complete.
- This playbook is an illustrative sample, and only works with S3 compatible MigStorage backends. You can swap out the Ansible block below if you aren't using S3.
- name: Download contents of Velero Backup from Bucket with S3 CLI
shell: aws s3 cp s3://{{ bucket_name }}/velero/backups/{{ backup_name }} {{ backup_local_dir }} --recursive
register: result
- This playbook doesn't verify that your installed
ocversion configured on$PATHcan perform the required conversion.- Start with the destination cluster
occlient version - If the destination cluster
occlient version doesn't work, keep trying, dropping back 1 minorocrelease each time. E.g. if destination cluster is 4.4, try using oc versions (4.4, 4.3, 4.2, 4.1, ...) until a version is found capable of the offline GVK conversion.
- Start with the destination cluster