Epic Goal

• Align the refactored version of the ANP proxy upstream to the product downstream

Why is this important?

• Current status:
  We have a downstream cluster-proxy-addon and an upstream cluster-proxy. Their abilities are alike but the cluster-proxy doesn't support OCP since it's designed for more common usability.

In this epic, we would like to refactor cluster-proxy-addon with cluster-proxy. We will use "cluster-proxy" to do the core proxy and tunnel. But the cluster-proxy-addon will be an adaptor to suit the OCP platform and respond to other squads' needs quickly.

The draft architecture would be:
https://app.excalidraw.com/l/6YsJahWEKqP/5RddUTdoMu7

Scenarios

1. ...

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. ...

Previous Work (Optional):

1. …

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>