Goal

Goal of this is to provide automated or semi-automated way to migrate existing cluster from Kuryr to OVNKubernetes

Why is this important?

We want users that cannot just reinstall clusters to have a migration path.

Scenarios

1. Migrate existing cluster from Kuryr to OVNKubernetes

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement

Dependencies (internal and external)

1. We need the migration to work, there were issues in 4.12.

Previous Work (Optional):

1. We'll utilize current migration code that allows OpenShiftSDN->OVNKubernetes.

Open questions::

1. Where to automate deleting OpenStack resources and finalizers.

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Technical Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>