-
Feature
-
Resolution: Done
-
Critical
-
None
-
Strategic Portfolio Work
-
False
-
-
False
-
OCPSTRAT-849Comprehensive In Cluster Networking configurations and customizations
-
0% To Do, 0% In Progress, 100% Done
-
0
-
Program Call
Feature Overview (aka. Goal Summary)
Add support to the OpenShift Installer to specify a custom MTU to be used for the cluster network
Goals (aka. expected user outcomes)
As a user, I need to be able to provide a custom MTU to be consumed by the OpenShift Installer so I can change the cluster network MTU on day-0
Requirements (aka. Acceptance Criteria):
The OpenShift Installer will accept another parameter through the install-config manifest that will be used as an option to change the default MTU value for the cluster network
Use Cases (Optional):
Customers who are running OpenShift on environments where the network traffic between the cluster and external endpoints is limited to a certain MTU. Some examples are OpenShift clusters running on public clouds like AWS, Azure or GCP where these clusters are connected to external services running on the customer premises via direct links, VPNs, etc... and limited to a certain MTU
Background
Additional background can be found in RFE-4009
Documentation Considerations
As a new option will be added to the Installer manifest this will need to be documented as any other.
- is caused by
-
FDP-164 Unexpected ICMP needs frag behavior in geneve tunnels
- Closed
- relates to
-
HIVE-2383 Add support to the Installer to specify a custom MTU for the cluster network
- New
-
RFE-4009 Installer MTU Override to support Edge Locations, Transit Gateway, Direct Connect etc
- Accepted
- links to