Feature Overview

With HyperShift, it is possible to host different cluster control-planes that make use of the same version. Furthermore, each cluster-control plane is composed of different components that "might" want to have their versions handled differently. Finally, HyperShift itself needs an own versioning scheme being an operator on its own. 

Goals

• The goal of this feature is to figure out how each of HyperShift's components should be versioned. 

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