NSM v1.4.0 is released via a set of example use cases.

Kubernetes Compatibility

NSM v1.4.0 has been successfully integration tested with Kubernetes versions:

• v1.24.0
• v1.23.0
• v1.22.1
• v1.21.1
• v1.20.7
• v1.19.11
• v1.18.15

And also with Calico CNI plugin.

Public Cloud Capability

NSM v1.4.0 has been tested on

• GKE
• AKS
• AWS
• bare metal in Equinix Metal
• Cross public clusters

Changes since v1.4.0

Advanced Healing: condition healing on datapath to NSE being down

When notified that the control path path is broken, check that the datapath to the NSE is also unreachable before healing. This will handle more robustly cases where there are temporary issues i the control path but the datapath is still functioning normally, reducing the circumstances underwhich a heal will be triggered.

See at Example

Breaking up an application monolith with NSM

There are many existing applications in the world which consist of a collection of monolith servers. Most of user also want to be able to progressively break such monoliths up into cloud native apps bit by bit by pulling services out into Pods. Planned to add a new application that will allow for monolith servers work with required application from k8s via NSM protocols.

See at Example

Update to Go 1.18

All NSM applications has been updated to go1.18.

Applications are only compiling with go 1.18. NSM API is still compatible with versions below 1.18.

Re-usuable workflows

Recently GitHub added a new kind of workflow that can be reused from different repos. We added this feature for nsm/sdk repository. See at the repository

Advanced vl3 examples

We added more vl3 examples

• vl3 network recovery examples

  • nscs death
  • nses death

• vl3 network over floating interdomain

• Scale vl3 network from zero

NSM+Application Service Mesh

We added NSM+Istio integration example via scale from zero pattern.

See at the example.

Dual-stack examples

We added IPv4 and IPv6 examples.

Connecting a remote interface without creating a VLAN on top

In order to facilitate a wider range of virtual environments hosting the Kubernetes cluster it could be feasible to allow the injection an interface into the NSC without creating a vlan on top.]

Stability improvements / bug fixes

Resolved bugs:

1. https://github.com/networkservicemesh/integration-k8s-packet/issues/261
2. https://github.com/networkservicemesh/deployments-k8s/issues/5676
3. https://github.com/networkservicemesh/sdk/issues/1276
4. https://github.com/networkservicemesh/deployments-k8s/issues/5599
5. https://github.com/networkservicemesh/integration-k8s-packet/issues/164
6. https://github.com/networkservicemesh/integration-k8s-aws/pull/311
7. https://github.com/networkservicemesh/integration-k8s-gke/pull/338
8. https://github.com/networkservicemesh/deployments-k8s/issues/6305
9. https://github.com/networkservicemesh/deployments-k8s/issues/6302
10. https://github.com/networkservicemesh/sdk/issues/1253