Bug 1787281 - Network optimization missing in 4.x Scaling and Performance Guide
Summary: Network optimization missing in 4.x Scaling and Performance Guide
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 4.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.4.z
Assignee: Ashley Hardin
QA Contact: Mike Fiedler
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-02 07:28 UTC by Frederic Giloux
Modified: 2020-12-11 18:58 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-11 18:58:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Frederic Giloux 2020-01-02 07:28:33 UTC 
Document URL: 
OCP 3.11 https://docs.openshift.com/container-platform/3.11/scaling_performance/network_optimization.html
missing in OCP 4.x

Section Number and Name:
- Optimizing Network Performance
- Optimizing the MTU for Your Network

Describe the issue: 
In OCP 3.x documentation we had this page with the recommendation among others of using a NIC supporting VxLAN offloading for pushing network bandwidth utilisation: https://docs.openshift.com/container-platform/3.11/scaling_performance/network_optimization.html
I could not find a similar page in OCP 4.x documentation. Is there any rational for it I am missing? As far as I understand the underlying technology has not changed.

Suggestions for improvement: 
Create a similar page for 4.x

Additional information: 
None
Comment 4 Ashley Hardin 2020-10-29 20:41:30 UTC 
WIP: https://github.com/openshift/openshift-docs/pull/26917
Comment 6 Ashley Hardin 2020-12-11 16:15:41 UTC 
QE approved in the PR
Comment 7 Ashley Hardin 2020-12-11 18:58:18 UTC 
The content is now published: https://access.redhat.com/documentation/en-us/openshift_container_platform/4.6/html/scalability_and_performance/optimizing-networking
Note You need to log in before you can comment on or make changes to this bug.