-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
Spikes for a Ephemeral Environments
-
False
-
-
False
-
RHIDP-4073Enhance QE framework for RHDH
-
To Do
-
RHIDP-4073 - Enhance QE framework for RHDH
-
QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
-
33% To Do, 0% In Progress, 67% Done
-
-
EPIC Goal
Currently, RHDH is leveraging only long running cluster (~3 clusters in IBM cloud) where the tests workloads are scheduled to run (e.g PR checks, nightly jobs, etc). This is expensive and wasteful. This epic aims to develop a POC for Ephemeral Environments to be used in RHDH CI system that will replace the long running clusters and will allow us to scale our support matrix and save on resources.
Challenges
- base url for RHDH is different with each spin-up of an ephemeral environment. This represents a problem, because GH App for authentication needs to have a callback url set which is every time different. The test suite heavily rely on the github oauth flow. Github does not provide an API for GH Apps creation. As part of this POC, we need to design a solution for this (either a reverse proxy, puppeteer UI automation for app creation, or something else)
- A framework needs to be selected that will automate the ephemeral env setup. One option to consider is: https://github.com/redhat-developer/mapt
Acceptance Criteria
- Spike on if MAPT tool is a viable for our case. Outlined Pros & Cons, or a proposal for a different tool.
- our contributions (eg. adding missing providers, etc) to MAPT are acceptable if MAPT is proven to be useful for our case
- Spike on how to handle github app creation to solve the challenge above
- POC for the github app flow automation
- POC - at least one working RHDH deployment on an ephemeral environment (of your choice - maybe on what is supported in MAPT if that is viable) is automated
- Documentation is provided both POC concepts.
- blocks
-
RHIDP-4024 [Automation] RHDH deployment on OpenShift Dedicated (OSD) on GCP using Operator
- To Do
- is related to
-
RHIDP-4552 [QE] Automate cluster setup on GKE
- Review