Table of contents
NSM v1.3.0 is released via a set of example use cases.
NSM v1.3.0 has been successfully integration tested with Kubernetes versions:
Public Cloud Capability
Changes since v1.2.0
Implementation of a virtual Layer 3 (vL3) Network Service(NS) that can be used to provide a common routing domain (or vrf) to which workloads in different clusters/cloud providers may attach.
Allow NSM to utilize external VPP instances it did not create itself. This would allow NSM and Calico-VPP to share a single VPP instance on a Node, improving performance in that case.
Note: You need only to change the CNI and NSM will work without any additional changes.
Enable Mutually Aware NSEs to overlap in IPAM/Routes
NSM by default presumes that all NSEs are ‘mutually ignorant’, meaning they do not know about each other. For this reason, if an NSM currently precludes ‘overlap’ in the assigned IPs and requested routes between the various NSEs to which a NSC is connected. Enabling Mutually Aware NSEs allows this limitation to be loosened in the case that two or more NSEs signal mutual awareness. This enables certain ‘multi-homing’ cases.
Update spire to v1.2.2
In this version SPIRE fixes a few critical performance issues. See at details https://github.com/spiffe/spire/releases/tag/v1.2.2
Update Policy Based Routing
The Policy Based Routing has been updated to support source port. There is a non-backward compatibility change in the API PolicyRoute message since the proto has been changed to string instead of uint32 and the port field has been removed and dst_port/src_port added.
Added possibility to update some properties of the IP Context of a connection from the NSC without having to close and re-request. Planned to improve it to support all IP context properties and add more examples.
Table of contents