Epic Goal

• Add the AWS PrivateLink functionality to the new PrivateLink controller.
• Configure AWS PrivateLink functionality to be mutually exclusive between the AWSPrivateLink controller and the new PrivateLink controller.
  • The PrivateLink controller should migrate status from the AWS PrivateLink Controller when selected.
  • The AWS PrivateLink controller should migrate status from the PrivateLink controller when selected.

Why is this important?

• The PrivateLink controller has a framework that enables cross-cloud functionality.
• The AWS PrivateLink controller is now redundant.

Scenarios

1. ...

Acceptance Criteria

• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. https://issues.redhat.com/browse/HIVE-2260

Open questions::

1. …

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>