-
Epic
-
Resolution: Unresolved
-
Blocker
-
None
-
Automate RHDH deployment on OpenShift Dedicated (OSD) on GCP
-
False
-
-
False
-
To Do
-
RHIDP-2476 - Support RHDH on OSD on GCP
-
QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
-
33% To Do, 0% In Progress, 67% Done
-
-
Feature
-
Rejected
-
-
EPIC Goal
Automate RHDH deployment on OpenShift Dedicated (OSD) on GCP
Background/Feature Origin
Red Hat Developer Hub (RHDH) needs to be deployable on various cloud platforms to meet customer demands. This epic focuses on automating the deployment process on OpenShift Dedicated (OSD) on Google Cloud Platform (GCP).
Why is this important?
Automating RHDH deployment on OSD on GCP will streamline the installation process, ensure consistency, and improve the overall user experience for platform engineers working with RHDH in this environment.
User Scenarios
- As a platform engineer, I want to easily deploy RHDH on OSD on GCP using automated processes
- As a developer, I want to verify RHDH installation using both Helm and Operator methods on OSD
- As an engineer, I want to understand the specific requirements and differences when deploying RHDH in an OSD environment
Dependencies (internal and external)
- Access to OpenShift Dedicated on GCP
- RHDH Helm charts and Operator
- Automation tools (e.g., Ansible, Terraform)
Acceptance Criteria
- Automated provisioning of OSD on GCP is successfully implemented
- Helm installation of RHDH on OSD is automated and verified
- Operator installation of RHDH on OSD is automated and verified
- Documentation for engineering is created, detailing the deployment process and OSD-specific considerations
- All automated processes are tested and validated in a production-like environment
Release Enablement/Demo - Provide necessary release enablement details and documents
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 Playwright: <link or reference to playwright>
QE - Automated tests merged: <link or reference to automated tests>
DOC - Downstream documentation merged: <link to meaningful PR>