-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
Progressive HyperShift Operator delivery for ROSA/HCP
-
False
-
None
-
False
-
Not Selected
-
To Do
-
OCPSTRAT-1713 - HyperShift automated delivery for ROSA/HCP
-
-
88% To Do, 13% In Progress, 0% Done
-
0
-
0
-
0
Goal
- Each HyperShift commit involving the HyperShift Operator gets delivered without manual intervention all the way to ROSA/HCP staging environment
Why is this important?
- Reduce HyperShift engineering release duty toil
- Ensure predictable delivery cadence
- Improve release visibility and tracking with Inscope
- Ensure consistent pipeline stages
- Leverage automated soaking time and roll out
Scenarios
- Merge queue in main:
- Prow gates that tests HyperShift in the HyperShift CI cluster
on-merge Konflux build - crt-redhat-acm HyperShift Operator application's Release plan admission pushes to prod-service registry
- HyperShift's app-interface saas.yaml gets triggered and modifies the HYPERSHIFT_OPERATOR_OVERRIDING_DATA variable for osd-fleet-manager-integration to the new prod-service build
- Trigger ROSA/HCP SD tests example from OSD
- Trigger HCP QE regression tests. Currently we trigger manually in Jenkins although there was bash tool
- On success, promote to stage
- Trigger ROSA/HCP SD tests
- Trigger HCP QE regression tests
- On success, promote to prod? (maybe not everytime, probably Mon/Wed)
- Prow gates that tests HyperShift in the HyperShift CI cluster
Acceptance Criteria
- Automated roll outs to production
- Troubleshooting documented in SOP
Dependencies (internal and external)
- app-interface
- Konflux
- Inscope
- OpenShift prow CI
Previous Work (Optional):
Useful links:
How to set up saas to reference new image
Open questions:
- What should be the follow-up for stage to prod?
- Should we use increasing release numbers for versions? Should we use dates? (semver doesn't seem to be in konflux automation ATM)
Done Checklist
- CI - CI is running, tests are automated and merged.
- HyperShift SOP describing the pipeline with troubleshooting steps <link to Feature Enablement Presentation>
- QE - Automated tests merged: <link or reference to automated tests>
- is related to
-
RHCLOUD-35534 Onboarding for HyperShift service
-
- Closed
-
- relates to
-
HOSTEDCP-671 Progressive Delivery process for the HyperShift Operator
-
- Closed
-