Uploaded image for project: 'OpenShift SDN'
  1. OpenShift SDN
  2. SDN-3857

Support for Custom machinepool MTU Configuration for ROSA Local Zones

    XMLWordPrintable

Details

    • Support for Custom machinepool MTU Configuration for ROSA Local Zones
    • False
    • None
    • False
    • Not Selected
    • To Do
    • OCPSTRAT-273 - Support for Custom machinepool MTU Configuration for ROSA Local Zones
    • 0
    • 0% 0%
    • XL
    • ---
    • 0
    • 0

    Description

      Epic Goal

      We already support to  lower the cluster-wide MTU to the Lowest Common Denominator one. We will do a design spike to investigate per path MTU and look to implement the same.

       

      Why is this important?

      • Issues on nodes in a different ROSA Local Zone
      • MTU is calculated based on what the Geneve overhead is
      • We use the MTU of the first node (if they did not specify one in the cluster config) minus the header overhead
      • We taint nodes whose MTU is too small and the node won’t go ready
      • You can change the MTU on a running cluster, so they can shrink down the MTU if needed
      • Perfscale has tested with 9k MTU, lowering the MTU will cost more

      Scenarios

      1. ...

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. …

      Open questions::

      1. …

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

      Attachments

        Issue Links

          depends on

          Bug - A problem that impairs or prevents the functions of the product. FDP-164 Unexpected ICMP needs frag behavior in geneve tunnels

          • Undefined - Priority not specified.
          • New
          is related to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SPLAT-657 AWS Local Zones - Phase II - IPI automation - Installer support to create resources in Local Zone for edge pool

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. SPLAT-1004 [aws][local-zones] Spike/Collaborate Path MTU Discovery (SDN team)

          • Critical - To be worked on immediately following BLOCKER issues.
          • To Do
          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SPLAT-1126 Add support to the Installer to specify a custom MTU for the cluster network

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Feature - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. OCPSTRAT-736 Add support to AWS Wavelength Zones

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              jcaamano@redhat.com Jaime Caamaño Ruiz
              ddharwar@redhat.com Deepthi Dharwar
              Ashley Hardin Ashley Hardin
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated: