-
Feature
-
Resolution: Unresolved
-
Normal
-
ACM 2.15.0, ACM 2.14.z
-
Product / Portfolio Work
-
False
-
-
False
-
Not Selected
-
Low
Feature Overview
The current support matrices (ACM/MCE) document a specific k8s version for EKS/AKS/GKE/IKS.
In order to meet the needs of our customers, we need to validate and document a range of k8s versions, eg just like we do today with OpenShift
Goals
- Provide test coverage for 3 versions of K8s
- Document via Support matrix by amending the EKS, IKS, AKS, GKE and CNCF conformant listings to include a version range eg [1.31 - 1.33]
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. |
YES |
| Updates to support matrices for 2.15 and 2.14 | This gives us coverage for current EUS 2.15, and 1 level back which is what the customer noted by the Support exception below | YES |
(Optional) Use Cases
This Section:
- As a fleet administrator, I want to manage a range of K8s offerings like EKS, AKS, as well as RH offerings like OCP, ROSA, ARO all within a single hub.
- As a fleet administrator, to keep costs lower, I want to use 1 hub to manage a range of K8s offerings like EKS, AKS, GKE, IKS
- As a fleet administrator, I also want to use CNCF conformant K8s like Rancher and Mirantis, and I want CNCF conformant clusters to have that same range of support offered by RH.
Questions to answer
- What is the optimal range of K8s versions to test and document into the support matrix?
- Do we need to go back to 2.13 to update those support matrices as well?
Out of Scope
- …
Background, and strategic fit
See support exception for customer point of view
https://issues.redhat.com/browse/SUPPORTEX-29034
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)?
