-
Epic
-
Resolution: Done
-
Normal
-
None
-
None
-
Create test pipeline for ocm hub support on EKS
-
False
-
None
-
False
-
Not Selected
-
To Do
-
ACM-13113 - Hub support on EKS
-
0% To Do, 0% In Progress, 100% Done
Feature Overview
As an internal feature, we would like to attempt running MCE hubs on EKS.
This could be a viable cost saving option to enable HCM engineering to run management hubs on EKS.
Goals
This Section: Provide high-level goal statement, providing user context
and expected user outcome(s) for this feature
- Understand the upstream work: https://github.com/open-cluster-management-io/enhancements/pull/125
- Understand the planning document: https://docs.google.com/document/d/16xoyBQVozW1mUmbjPS6mt9yUN5RIS4Brapcxkjbn5sc/edit?usp=sharing
- As an HCM engineer I would like to deploy EKS (somehow, separately) and then run the open-cluster-management components on it which provides a basis for leveraging HyperShift for hosted clusters.
Requirements
This Section: A list of specific needs or objectives that a Feature must
deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
it does not shift the feature.
| Requirement | Notes | isMvp? |
|---|---|---|
| CI - MUST be running successfully with test automation | This is a requirement for ALL features. |
YES |
| Release Technical Enablement | Provide necessary release enablement details and documents. |
NO |
| implement a simple e2e testing flow that runs on a cron basis conducting some basic EKS e2e OCM-io cluster registration tests. | The actual test involves cloning the repo, running a make command, and checking the response code. The QE team doesn't need to worry about the test logic, just setting up the pipeline. | YES |
(Optional) Use Cases
This Section:
- An internal Red Hat user can be sure that the EKS upstream enhancement works for o-c-m cluster registration.
- An upstream o-c-m user can see that the EKS upstream enhancement works for o-c-m cluster registration
Questions to answer
- Will this ever be customer facing?
Out of Scope
- Cluster lifecycle of EKS itself.
Background, and strategic fit
This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?
Assumptions
- ...
Customer Considerations
- ...
Documentation Considerations
Questions to be addressed:
- What educational or reference material (docs) is required to support this
product feature? For users/admins? Other functions (security officers, etc)? - Does this feature have a doc impact?
- New Content, Updates to existing content, Release Note, or No Doc Impact
- If unsure and no Technical Writer is available, please contact Content
Strategy. - What concepts do customers need to understand to be successful in
[action]? - How do we expect customers will use the feature? For what purpose(s)?
- What reference material might a customer want/need to complete [action]?
- Is there source material that can be used as reference for the Technical
Writer in writing the content? If yes, please link if available. - What is the doc impact (New Content, Updates to existing content, or
Release Note)?
