Loading...

XML

Word

Printable

Type: Epic
Resolution: Unresolved
Priority: Major
Fix Version/s: ACM 2.17.0
Affects Version/s: None
Component/s: Cluster Lifecycle, Hive, HyperShift, Installer, Server Foundation
Labels:

Epic Name:
Develop mechanism to update HIVE more regularly
Activity Type:
Future Sustainability
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Color Status:
Not Selected
Epic Status:
In Progress
Feature Link:
ACM-27070 - ACM 2.16.0 / MCE 2.11.0 Installer Engineering Improvements / Tasks
Latest Status Summary:

Hide
2.18.26 (Status same as before)

Shay has reached out to me indicating he has begun the automatic synchronization work. Timeline is looking good! This ticket is still planned for 2.17, but component teams have indicated they are willing to do the work early in the cycle so we can synchronize *during* 2.17 dev cycle, not at the end of it.

Show
2.18.26 (Status same as before) Shay has reached out to me indicating he has begun the automatic synchronization work. Timeline is looking good! This ticket is still planned for 2.17, but component teams have indicated they are willing to do the work early in the cycle so we can synchronize *during* 2.17 dev cycle, not at the end of it.
Parent Link:
ACM-27070ACM 2.16.0 / MCE 2.11.0 Installer Engineering Improvements / Tasks
Hierarchy Progress Bar:

14% To Do, 43% In Progress, 43% Done

Severity:
Low

SFDC Cases Links:
SFDC Cases Open:
SFDC Cases Counter:

PX Impact Score:

Intelligence Requested:
Market:

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

is cloned by

ACM-26538 Synchronize HIVE SHA across ACM Z-Streams (fe9c66be8e113d4268ab744ca708860d0b4cc6e1)

Closed

Assignee:: Nathaniel Graham

Reporter:: To Hung Sze

QA Contact:: Hui Chen

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Created:: 2025/11/06 3:41 PM

Updated:: 2026/02/18 11:33 PM

Details

Description

Resolution

Investigation

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates