Epic Goal

• The OpenShift Installer will default OVN Kubernetes instead OpenShift SDN as the default networking plugin on every provider we support

Why is this important?

• OVN Kubernetes will be the default networking plugin in 4.12. The installer is actually using OpenShift SDN as the default network plugin for every provider (apart from SNO which is OVN already and OpenShift SDN is blocked) we support so we need to change the installer behaviour going forward to use OVN Kubernetes instead. 

Scenarios

1. While using the OpenShift Installer, the install-config manifest will take OVN as the default entry for networking.networkType instead of OpenShiftSDN

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.

Dependencies (internal and external)

1. The SDN team has validated every single provider we support works with OVN

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release 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>