OCP/Telco Definition of Done
Epic Template descriptions and documentation.

<--- Cut-n-Paste the entire contents of this description into your new Epic --->

Epic Goal

• Enable OpenShift to support private and restricted GCP API endpoints while deploying the platform on GCP as we do for AWS already

Why is this important?

• Customers in regulated industries need a way to consume private endpoints when deploying OpenShift in GCP to be compliant with their regulatory policies.

Scenarios

1. As an OpenShift Admin, I want to be able to use GCP Private API endpoints while deploying OpenShift so I can be compliant with my company security policies
2. As an OpenShift Admin, I want to be able to use GCP Restricted API endpoints while deploying OpenShift so I can be compliant with my company security policies

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Be able to use GCP Private API endpoints for OpenShift on GCP deployments.
• Be able to use GCP Restricted API endpoints for OpenShift on GCP deployments.

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>