We drive OpenShift cross-market customer success and new customer adoption with constant improvements and feature additions to the existing capabilities of our OpenShift Core Networking (SDN, Network Edge, Network Observability). This feature captures that natural progression of the product for that development that does not align neatly to an existing Jira Feature for Network Plumbing.

Goals

• Feature enhancements (performance, scale, configuration, UX, ...)
• Modernization (incorporation and productization of new technologies)

Requirements

• Core Networking Stability
• Core Networking Performance and Scale
• Core Neworking Extensibility (e.g. Multus CNIs)
• Core Networking UX (Observability)
• Core Networking Security and Compliance

In Scope

•  Network plumbing includes migration btw CNIs, Multus, OVN as secondary network, Microshift work and other  traffic routing etc.

Out of Scope

There are grey areas, but in general:

• CNV
• Service Mesh
• CNF
• Telco-specific customer solutions (versus in-product features)

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