8000 Feature Request: To allow specifying mtu and advmss values under routes -> config. · Issue #2881 · nmstate/nmstate · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Feature Request: To allow specifying mtu and advmss values under routes -> config. #2881

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
iamfaad opened this issue Apr 10, 2025 · 7 comments
Open

Feature Request: To allow specifying mtu and advmss values under routes -> config. #2881

iamfaad opened this issue Apr 10, 2025 · 7 comments

Comments

@iamfaad
Copy link
iamfaad commented Apr 10, 2025

Hi Team,
I have two openshift clusters across two DCs, openshift clusters are deployed with jumbo frames (9000mtu) however the path inbetween doesnot support jumbo and support 1500mtu only.
I am using separate vlan to for the communication between these two clusters for which i am specifying routes via nmstate nncp, however i do not see any option avaiable to define the mtu in nmstate nncp.
Can team please add these options so i can manage all routes through nncp only instead of defining it via nmcli or by creating machineconfig which will result in mcp rollout whenever i needed to add any new route.
@cathay4t
Copy link
Member

The MTU of route is supported since 2.2.42+.

We need to code out the support of advmss, but it should be very simple.

@iamfaad
Copy link
Author
iamfaad commented Apr 10, 2025

Below is the available/supported configuration

apiVersion: nmstate.io/v1
kind: NodeNetworkConfigurationPolicy
metadata:
  name: $nncp_name
spec:
  nodeSelector:
    node-role.kubernetes.io/worker: ""
  desiredState: 
   routes:
     config: 
     - destination: 10.21.x.x/24
       next-hop-address: 10.x.x.1
       next-hop-interface: bond0.101
       metric: 400

however i am requesting for configuration which supports mtu or advmss option as well as under;

apiVersion: nmstate.io/v1
kind: NodeNetworkConfigurationPolicy
metadata:
  name: $nncp_name
spec:
  nodeSelector:
    node-role.kubernetes.io/worker: ""
  desiredState: 
   routes:
     config: 
     - destination: 10.21.x.x/24
       next-hop-address: 10.x.x.1
       next-hop-interface: bond0.101
       metric: 400
       mtu: 1500    <------------ nncp to support this option.
       advmss: 1500 <------------ nncp to support this option.

Please support.

@iamfaad
Copy link
Author
iamfaad commented Apr 10, 2025

The MTU of route is supported since 2.2.42+.

We need to code out the support of advmss, but it should be very simple.

Hi,

i am referring to allow this option via nodenetworkconfigurationpolicy (nncp) via nmstate operator.

Regards

@iamfaad
Copy link
Author
iamfaad commented Apr 10, 2025

Hi,
I just checked the change log seems that the option is there, let me see if new release is available from the operator hub catalog.

@iamfaad iamfaad changed the title Feature Request: To allow specifying mtu and advmss value while under routes -> config. Feature Request: To allow specifying mtu and advmss values under routes -> config. Apr 10, 2025
@iamfaad
Copy link
Author
iamfaad commented Apr 10, 2025

I am running with ocp version 4.14 and it seems that this version is not shipped for 4.14. I installed latest nmstate operator and it shipped with nmstate 2.2.39-3

@iamfaad
Copy link
Author
iamfaad commented Apr 18, 2025

Hi Team,
I tried ocp version 4.16.36 where nmstate operator equipped with package nmstate-2.2-40, still mtu option doesnot work there.

@iamfaad
Copy link
Author
iamfaad commented Apr 18, 2025

++adding ss.

Image
Image
Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cathay4t @iamfaad
0