Epic Goal

As an OpenShift installation administrator, I want to configure OpenShift to have separate networks for the management traffic and the service traffic.

Why is this important?

Customer architecture designs involve isolating the control traffic in its own network. This is a general best practice requested for OpenShift clusters. Isolation of the management traffic provides a dedicated communication channel for managing OpenShift clusters, which provides higher security and reliability by separating service and management traffic.

Acceptance Criteria

• Users can specify a CIDR dedicated to management traffic and separate from the service traffic.
• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.

Dependencies (internal and external)

None

Open questions

None

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>