-
Epic
-
Resolution: Done
-
Blocker
-
None
-
GCP Service Account Authentication
-
False
-
None
-
False
-
Not Selected
-
Done
-
Impediment
-
0% To Do, 0% In Progress, 100% Done
-
Approved
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
- Allow installer to deploy a cluster while authenticating the installer with the service account attached to a GCP VM
Why is this important?
- Allows users to deploy GCP clusters without downloading a service account json file
Scenarios
- Deploying a GCP cloud deployment from a GCP VM
Acceptance Criteria
- 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::
- …
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>
- is related to
-
CORS-1292 Support users in organizations that only have access to the account where the cluster needs to be created using AssumeRole like work-flows
- Closed
- links to
- mentioned on
There are no Sub-Tasks for this issue.