Skip to content
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.

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

Automated cherry pick of #4419: Set NO_FLOOD to IPsec tunnel ports #4470: Fix that Service routes may get lost when starting on Windows #4654: Restore NO_FLOOD to OVS ports after reconnecting the OVS #4711: Fix route deletion for Service ClusterIP and LoadBalancerIP #4761

Commits on Mar 24, 2023

  1. Set NO_FLOOD to IPsec tunnel ports

    Set NO_FLOOD to IPsec tunnel ports to avoid ARP flooding.
    
    Signed-off-by: Xu Liu <[email protected]>
    xliuxu authored and luolanzone committed Mar 24, 2023
    Configuration menu
    Copy the full SHA
    207df52 View commit details
    Browse the repository at this point in the history
  2. Fix that Service routes may get lost when starting on Windows

    Fix antrea-io#4467
    
    Signed-off-by: Hongliang Liu <[email protected]>
    hongliangl authored and luolanzone committed Mar 24, 2023
    Configuration menu
    Copy the full SHA
    35b57b6 View commit details
    Browse the repository at this point in the history
  3. Restore NO_FLOOD to OVS ports after reconnecting the OVS bridge

    The NO_FLOOD configuration is lost when the OVS daemon is restarted.
    Currently, the only way to recover this configuration is by restarting
    the agent. This pull request adds logic to recover the configuration
    when receiving OVS reconnection events.
    
    Signed-off-by: Xu Liu <[email protected]>
    xliuxu authored and luolanzone committed Mar 24, 2023
    Configuration menu
    Copy the full SHA
    a82b522 View commit details
    Browse the repository at this point in the history

Commits on Mar 27, 2023

  1. Fix route deletion for Service ClusterIP and LoadBalancerIP

    When proxyAll is enabled, AntreaProxy needs to install routes in the
    host network namespace to redirect traffic to OVS for load balancing.
    For a Service with multiple ports, multiple ServicePorts are generated
    and processed. The previous code installed the route for a ClusterIP or
    a LoadBalancerIP multiple times when such a Service was created, and
    uninstalled the route multiple times when it was deleted, leading to a
    few problems.
    
    This patch adds a serviceIPRouteReferences which tracks the references
    of Service IPs' routes. The key is the Service IP and the value is the
    the set of ServiceInfo strings. With the references, we install a route
    exactly once as long as it's used by any ServicePorts and uninstall it
    exactly once when it's no longer used by any ServicePorts.
    
    This patch also fixes an issue that the route for ClusterIP was not
    removed on Windows Nodes after the Service was removed.
    
    Fixes antrea-io#4361
    
    Signed-off-by: Quan Tian <[email protected]>
    tnqn authored and luolanzone committed Mar 27, 2023
    Configuration menu
    Copy the full SHA
    5805858 View commit details
    Browse the repository at this point in the history

Commits on Mar 29, 2023

  1. Fix windows image building error in jenkins pipeline (antrea-io#4697)

    DOCKER_REGISTRY is no longer needed in agent image tag.
    Remove it to align with containerd image tag in CI pipeline.
    
    Update more image tags which is unavailable in public repo.
    
    Fixes antrea-io#4696
    
    Signed-off-by: Shuyang Xin <[email protected]>
    XinShuYang authored and luolanzone committed Mar 29, 2023
    Configuration menu
    Copy the full SHA
    a1e9dba View commit details
    Browse the repository at this point in the history

Commits on Mar 30, 2023

  1. Ensure OVS port is valid before setting NO_FLOOD (antrea-io#4674)

    There could be some cases that OVS ports are left invalid. Setting
    NO_FLOOD for these ports will fail for sure and restarting agents would
    just meet the same error. Later we should enhance the port cleanup
    logic, either when they are firstly identified, or when their owners do
    the initialization. For now, as there could be invalid ports in
    interface cache, we should ensure a port is valid before setting
    NO_FLOOD.
    
    Signed-off-by: Quan Tian <[email protected]>
    tnqn authored and luolanzone committed Mar 30, 2023
    Configuration menu
    Copy the full SHA
    3a2c2d7 View commit details
    Browse the repository at this point in the history