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

Separate tunnel map key and value structure #17106

Closed
wants to merge 1 commit into from

Commits on Sep 7, 2021

  1. Separate tunnel map key and value structure

    Tunnel map use same endpoint_key as key and value structure. in future
    we may add tunnel map value structure fields for new features like
    extending cilium VXLAN tunnel connectivity to external VXLAN devices and
    add value fields like VNI and VTEP MAC...etc, We also need to add cilium
    bpf tunnel command for users to maintain the tunnel map, thus separate the
    tunnel map value and key structure as first step toward that goal
    
    Now we separated tunnel map key and value structure, the encrypt key is
    kept in new value structure tunnel_endpoint_info, key is not needed in endpoint_key
    
    Suggested-by: Kornilios Kourtis <kornilios@isovalent.com>
    Suggested-by: Joe Stringer joe@cilium.io
    Signed-off-by: Vincent Li vincent.mc.li@gmail.com
    vincentmli committed Sep 7, 2021
    Configuration menu
    Copy the full SHA
    4cbf902 View commit details
    Browse the repository at this point in the history