-
Epic
-
Resolution: Done
-
Major
-
None
-
Develop mechanism to update HIVE more regularly
-
Future Sustainability
-
False
-
-
False
-
Not Selected
-
In Progress
-
ACM-27070 - ACM 2.16.0 / MCE 2.11.0 Installer Engineering Improvements / Tasks
-
-
-
0% To Do, 0% In Progress, 100% Done
-
Low
Resolution
As an engineer in ACM, I want to be able to update HIVE to their latest more frequently. Using the MintMaker configuration supplied by rh-ee-dhaiduce (here), we will automate the creation of Hive API update PRs within each of the components' repos weekly, on Mondays.
Investigation
The following concerns should be addressed:
- how to maintain sufficient for z-stream
- how to handle updates that require specific / additional testing
- what other components / teams need to be notified before/after the update
The mechanism must account for all of the following:
- When bumping hive, you must bump all the things: the container image ref, CRDs, RBAC, the hive-operator Deployment, etc. When these get out of sync, we have Problems™.
- When bumping hive, programmatic consumers of hive APIs (at least Assisted Installer. Others? Please make a complete list below.) must revendor to pick up CRD changes. When these get out of sync, we have Problems™.
- Server Foundation work example: https://issues.redhat.com/browse/ACM-26426
- Site Config work example: https://issues.redhat.com/browse/ACM-26432
- Assisted Installer work example: https://issues.redhat.com/browse/ACM-26433
