Feature Overview

When I manage a fleet of OpenShift and Kubernetes clusters, I need to be able to manage a range of versions. For example I can manage 4 versions of OpenShift at the hub.

I need that same range of versions for my Kubernetes clusters.

Goals

• provide test coverage, as necessary, for 4 versions of K8s for EKS/GKE/AKS/IKS
• include support matrix, for 4 versions of K8s for EKS/GKE/AKS/IKS

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.

(Optional) Use Cases

This Section:

• Main success scenarios - high-level user stories
• Alternate flow/scenarios - high-level user stories
• ...

Questions to answer

• Legit question: do we even need to do any additional testing with the EKS/AKS/GKE/IKS? Since OCP == K8S and we already test a range of 4 versions of OCP, I suspect this could be a testing no-op.

Out of Scope

• …

Background, and strategic fit

As OpenShift is Kubernetes, do understand that as we already ship ACM hubs with support coverage for 4 releases of OpenShift, it means we are in fact already testing 4 versions of Kubernetes.

So we are matching that existing 4 version of OCP coverage to include K8s API version as well.

For example with ACM 2.13 we document 4 OCP versions of support:

As for K8s API versions we only explicitly list 1 version:

Hence we should instead document a range of K8s versions like this

Amazon EKS [Kubernetes 1.29 - 1.32]

Azure AKS [Kubernetes 1.29 - 1.32] 

etc

Assumptions

• ...

Customer Considerations

• Customers are expecting this, slack thread, and Support Exception request

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)?