networkservicemesh · denis-tingaikin · Dec 28, 2024
diff --git a/content/docs/releases/history.md b/content/docs/releases/history.md
@@ -6,8 +6,8 @@ weight = 2
 ## 1.14
 
 **Latest Release:** 1.14.0 (released: 2024-09-20)\
-**Patch Releases:** [1.14.0](../v1.14.0)\
-**Kubernetes support:**  v1.21, v1.22, v1.23, v1.24, v1.25, v1.26, v1.27, v1.28
+**Patch Releases:** [1.14.0](../v1.14.0), [1.14.1](../v1.14.1), [1.14.2](../v1.14.2)\
+**Kubernetes support:**  v1.21, v1.22, v1.23, v1.24, v1.25, v1.26, v1.27, v1.28, 1.29
 
 ## 1.13
 

diff --git a/content/docs/releases/v1.10.0.md b/content/docs/releases/v1.10.0.md
@@ -49,27 +49,30 @@ panic: error: VPPApiError: System call error #6 (-16)
 
 ### AKS: AF_XDP support
 
-
-Root issue: https://github.com/networkservicemesh/cmd-forwarder-vpp/issues/859
-
-AF_XDP socket doesn't work on AKS cluster
+
+
+Root issue: https://github.com/networkservicemesh/cmd-forwarder-vpp/issues/859
+
+AF_XDP socket doesn't work on AKS cluster
 Ping works only without `hostNetwork: true` flag.
 
 [See more details](https://github.com/networkservicemesh/integration-k8s-aks/issues/282)
 
 
 ### GKE: AF_XDP support
 
-
-Root issue: https://github.com/networkservicemesh/cmd-forwarder-vpp/issues/859
-
-AF_XDP socket doesn't work on GKE cluster
-Logs:
-```
-Apr  3 05:38:16.954 [INFO] [cmd:vpp] libbpf: Kernel error message: virtio_net: XDP expects header/data in single page, any_header_sg required
-Apr  3 05:38:16.954 [INFO] [cmd:vpp] vpp[10244]: af_xdp: af_xdp_load_program: bpf_set_link_xdp_fd(eth0) failed: Invalid argument
-Apr  3 05:38:18.228 [ERRO] [cmd:/bin/forwarder] [duration:12.809608ms] [hostIfName:eth0] [vppapi:AfXdpCreate] VPPApiError: System call error #6 (-16)
-panic: error: VPPApiError: System call error #6 (-16)
+
+
+Root issue: https://github.com/networkservicemesh/cmd-forwarder-vpp/issues/859
+
+AF_XDP socket doesn't work on GKE cluster
+Logs:
+
+```
+Apr  3 05:38:16.954 [INFO] [cmd:vpp] libbpf: Kernel error message: virtio_net: XDP expects header/data in single page, any_header_sg required
+Apr  3 05:38:16.954 [INFO] [cmd:vpp] vpp[10244]: af_xdp: af_xdp_load_program: bpf_set_link_xdp_fd(eth0) failed: Invalid argument
+Apr  3 05:38:18.228 [ERRO] [cmd:/bin/forwarder] [duration:12.809608ms] [hostIfName:eth0] [vppapi:AfXdpCreate] VPPApiError: System call error #6 (-16)
+panic: error: VPPApiError: System call error #6 (-16)
 ```
 
 [See more details](https://github.com/networkservicemesh/integration-k8s-gke/issues/383)
@@ -124,14 +127,16 @@ Generated commands could be re-used in performance testing to keep performance t
 
 ### NSC - Add support for K8S PSS restricted/baseline profiles (for hostPath volumes)
 
-K8S 1.25 release deprecates PSP (Pod security policy) and enables PSS (Pod Security Standards)/PSA (Pod Security Admission controller) by default. The PSS has 3 profiles - Privileged, Baseline and Restricted. 
-NSC requires hostPath volumes for unix sockets. HostPath volumes are not permitted in Baseline/Restricted profiles. 
+K8S 1.25 release deprecates PSP (Pod security policy) and enables PSS (Pod Security Standards)/PSA (Pod Security Admission controller) by default. The PSS has 3 profiles - Privileged, Baseline and Restricted.
+NSC requires hostPath volumes for unix sockets. HostPath volumes are not permitted in Baseline/Restricted profiles.
 
 Need a solution for NSC to work in Baseline/Restricted profiles.
 
 Couple of options:
+
 - NSM CSI driver : Add a NSM CSI driver plugin to mount the hostPath volume.
 - Use network sockets instead of unix sockets and eliminate the need for hostPath volume.
+
 <!--- Try to give a general description (optional if it overlaps with the content from the Google Docs file) -->
 
 [See more details](https://github.com/networkservicemesh/deployments-k8s/issues/9218)

diff --git a/content/docs/releases/v1.11.0.md b/content/docs/releases/v1.11.0.md
@@ -57,16 +57,17 @@ Status: RESOLVED.
 
 ### Add interdomain healing examples
 
-Currently, we don't test healing over interdomain or floating interdomain. So we could add some examples of how to do that.
-
-Scenarios:
-- Forwarders death in floating interdomain scenario
-- NSE death in floating interdomain scenario
-- NSM systems death in floating interdomain scenario
-- Proxy nsmgrs death in interdomain scenario
-- NSMGRs death in interdomain scenario
-- Registry death in interdomain scenario
-
+Currently, we don't test healing over interdomain or floating interdomain. So we could add some examples of how to do that.
+
+Scenarios:
+
+- Forwarders death in floating interdomain scenario
+- NSE death in floating interdomain scenario
+- NSM systems death in floating interdomain scenario
+- Proxy nsmgrs death in interdomain scenario
+- NSMGRs death in interdomain scenario
+- Registry death in interdomain scenario
+
 We need to check scenarios from single cluster testing in multicluster scenarios.
 
 [See more details](https://github.com/networkservicemesh/deployments-k8s/issues/9647)
@@ -138,9 +139,9 @@ Status: RESOLVED.
 
 ### `Update dependent repositories` workflow does update incorrectly
 
-`integration-k8s-kind` re-uses [.github workflow](https://github.com/networkservicemesh/.github/blob/main/.github/workflows/update-dependent-repositories-gomod.yaml)
-This is wrong, because this workflow updates `integration-k8s-kind` instead of `integration-tests` in dependent repositories (public clusters).
-For example:
+`integration-k8s-kind` re-uses [.github workflow](https://github.com/networkservicemesh/.github/blob/main/.github/workflows/update-dependent-repositories-gomod.yaml)
+This is wrong, because this workflow updates `integration-k8s-kind` instead of `integration-tests` in dependent repositories (public clusters).
+For example:
 https://github.com/networkservicemesh/integration-k8s-kind/actions/runs/5656999510/job/15325140836
 
 [See more details](https://github.com/networkservicemesh/integration-k8s-kind/issues/862)

diff --git a/content/docs/releases/v1.12.0.md b/content/docs/releases/v1.12.0.md
@@ -226,12 +226,12 @@ Status: RESOLVED.
 
 ### Improve cronjob for CVEs scanning in docker images
 
-
-1. Add image names in CVEs reports
-2. Remove old results on every CVEs scanning
-3. Fix the period of the cronjob
 
 
+1. Add image names in CVEs reports
+2. Remove old results on every CVEs scanning
+3. Fix the period of the cronjob
+
 [See more details](https://github.com/networkservicemesh/deployments-k8s/issues/10726)
 
 
@@ -288,35 +288,38 @@ It looks like alpine:3.19's curl doesn't accept such DNS responses. I tried to m
 
 ### External NSC fix interface problem
 
-
-Hi all, I was testing the example related to the configuration of an [external client](https://github.com/networkservicemesh/deployments-k8s/tree/main/examples/k8s_monolith/external_nsc) to the cluster and noticed how the configuration of the MetalLB LoadBalancer needs to be changed.
-In fact, in the [guide](https://kind.sigs.k8s.io/docs/user/loadbalancer/) offered by Kind, it is pointed out that the method through the ConfigMap is no longer supported.
-One should run these commands
-
-```
-`kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.13.7/config/manifests/metallb-native.yaml`
-```
-
-```
-
-kubectl wait --namespace metallb-system \
-                --for=condition=ready pod \
-                --selector=app=metallb \
-                --timeout=90s
-```
-```
-` kubectl apply -f https://kind.sigs.k8s.io/examples/loadbalancer/metallb-config.yaml`
-```
-I tried to open a pull request  to make noticed this, but it failed. 
-I followed the instructions inside the example, but apparently the external docker fails to communicate with the service: in fact the 2 kernel interfaces that should be available, are not created. 
-I don't know if it affects the order but this is what I followed:
-LoadBalancer , via the commands provided above and offered by the guide;
-[`DNS,`](https://github.com/networkservicemesh/deployments-k8s/tree/main/examples/k8s_monolith/external_nsc/dns);
-[External Docker](https://github.com/networkservicemesh/deployments-k8s/tree/main/examples/k8s_monolith/external_nsc/docker);
-[Spire](https://github.com/networkservicemesh/deployments-k8s/tree/main/examples/spire/single_cluster);
-[SPIFFE](https://github.com/networkservicemesh/deployments-k8s/tree/main/examples/k8s_monolith/external_nsc/spiffe_federation) ;
-I then ran the [command](https://github.com/networkservicemesh/deployments-k8s/tree/main/examples/k8s_monolith/external_nsc) to configure the cluster with the NSM resources, and finally the deployment for the [example](https://github.com/networkservicemesh/deployments-k8s/tree/main/examples/k8s_monolith/external_nsc/usecases/Kernel2IP2Kernel).
-
+
+
+Hi all, I was testing the example related to the configuration of an [external client](https://github.com/networkservicemesh/deployments-k8s/tree/main/examples/k8s_monolith/external_nsc) to the cluster and noticed how the configuration of the MetalLB LoadBalancer needs to be changed.
+In fact, in the [guide](https://kind.sigs.k8s.io/docs/user/loadbalancer/) offered by Kind, it is pointed out that the method through the ConfigMap is no longer supported.
+One should run these commands
+
+```
+`kubectl apply -f https://raw.githubusercontent.com/metallb/metallb/v0.13.7/config/manifests/metallb-native.yaml`
+```
+
+```
+
+kubectl wait --namespace metallb-system \
+                --for=condition=ready pod \
+                --selector=app=metallb \
+                --timeout=90s
+```
+
+```
+` kubectl apply -f https://kind.sigs.k8s.io/examples/loadbalancer/metallb-config.yaml`
+```
+
+I tried to open a pull request  to make noticed this, but it failed.
+I followed the instructions inside the example, but apparently the external docker fails to communicate with the service: in fact the 2 kernel interfaces that should be available, are not created.
+I don't know if it affects the order but this is what I followed:
+LoadBalancer , via the commands provided above and offered by the guide;
+[`DNS,`](https://github.com/networkservicemesh/deployments-k8s/tree/main/examples/k8s_monolith/external_nsc/dns);
+[External Docker](https://github.com/networkservicemesh/deployments-k8s/tree/main/examples/k8s_monolith/external_nsc/docker);
+[Spire](https://github.com/networkservicemesh/deployments-k8s/tree/main/examples/spire/single_cluster);
+[SPIFFE](https://github.com/networkservicemesh/deployments-k8s/tree/main/examples/k8s_monolith/external_nsc/spiffe_federation) ;
+I then ran the [command](https://github.com/networkservicemesh/deployments-k8s/tree/main/examples/k8s_monolith/external_nsc) to configure the cluster with the NSM resources, and finally the deployment for the [example](https://github.com/networkservicemesh/deployments-k8s/tree/main/examples/k8s_monolith/external_nsc/usecases/Kernel2IP2Kernel).
+
 Do you have any hints for solving this problem?
 
 [See more details](https://github.com/networkservicemesh/deployments-k8s/issues/10580)

diff --git a/content/docs/releases/v1.13.0.md b/content/docs/releases/v1.13.0.md
@@ -30,6 +30,13 @@ Status: RESOLVED.
 [See more details](https://github.com/networkservicemesh/deployments-k8s/issues/2010)
 
 
+### vl3 healing
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/cmd-nse-vl3-vpp/issues/289)
+
+
 ## System stability fixes and improvements
 
 
@@ -161,20 +168,21 @@ Status: RESOLVED.
 
 ### Logging system problems
 
-
-**1. Increase log file size** - https://github.com/networkservicemesh/integration-tests/issues/2917
-**2. Tests from different suites but with the same name overwrite each other.**
-For example:
-a. Run `TestBasicSuite/TestKernel2Kernel`
-b. Save logs to `ns-kerenel2kernel`
-c. Run `TestMemorySuite/TestKernel2Kernel`
-d. `ns-kerenel2kernel` logs will be overwritten
-**3. Logs are not complete.**
-For example:
-a. The last bash command from one of the healing test runs at
-`time=2024-01-19T13:51:50Z level=info msg=1 TestRunHealSuite/TestRemote_nsmgr_remote_endpoint=exitCode`
-b. But the last line in cmd-nsc logs is:
-`Jan 19 13:50:39.017[37m [TRAC] [id:alpine-beef03a3-a58e-48a5-9100-d853c81da3de-0] `
+
+
+**1. Increase log file size** - https://github.com/networkservicemesh/integration-tests/issues/2917
+**2. Tests from different suites but with the same name overwrite each other.**
+For example:
+a. Run `TestBasicSuite/TestKernel2Kernel`
+b. Save logs to `ns-kerenel2kernel`
+c. Run `TestMemorySuite/TestKernel2Kernel`
+d. `ns-kerenel2kernel` logs will be overwritten
+**3. Logs are not complete.**
+For example:
+a. The last bash command from one of the healing test runs at
+`time=2024-01-19T13:51:50Z level=info msg=1 TestRunHealSuite/TestRemote_nsmgr_remote_endpoint=exitCode`
+b. But the last line in cmd-nsc logs is:
+`Jan 19 13:50:39.017[37m [TRAC] [id:alpine-beef03a3-a58e-48a5-9100-d853c81da3de-0] `
 More than 1 min missed
 
 [See more details](https://github.com/networkservicemesh/integration-tests/issues/3420)

diff --git a/content/docs/releases/v1.13.1.md b/content/docs/releases/v1.13.1.md
@@ -27,6 +27,13 @@ NSM v1.13.1 has been tested on:
 
 
 
+### Dataplane part of `forwarder-vpp` leaks
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/cmd-forwarder-vpp/issues/1120)
+
+
 ### grpc produces leaks in NSM apps
 
 It seems like the current version of grpc is leaking

diff --git a/content/docs/releases/v1.14.0.md b/content/docs/releases/v1.14.0.md
@@ -2,7 +2,7 @@
 +++
 short="v1.14.0"
 title = "Release v1.14.0"
-date="2024-09-20 00:00:00 +0000 UTC"
+date="2024-07-18 00:00:00 +0000 UTC"
 +++
 
 
@@ -34,9 +34,16 @@ Status: RESOLVED.
 [See more details](https://github.com/networkservicemesh/deployments-k8s/issues/12279)
 
 
+### vl3 healing
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/cmd-nse-vl3-vpp/issues/289)
+
+
 ### Add dual stack support 
 
-Currently vL3-endpoint only support single stack:
+Currently vL3-endpoint only support single stack:
 https://github.com/networkservicemesh/cmd-nse-vl3-vpp/blob/main/main.go
 
 [See more details](https://github.com/networkservicemesh/cmd-nse-vl3-vpp/issues/261)
@@ -51,14 +58,14 @@ Status: RESOLVED.
 
 ### Memory leak in metrics chain element
 
-
-
-We should fix leaks in metrics chain element 
-
-![image](https://github.com/networkservicemesh/sdk/assets/49399980/4e805d41-fbb6-459a-ab87-8011be1fb474)
-
-
-
+
+
+We should fix leaks in metrics chain element 
+
+![image](https://github.com/networkservicemesh/sdk/assets/49399980/4e805d41-fbb6-459a-ab87-8011be1fb474)
+
+
+
 Sub task of https://github.com/networkservicemesh/cmd-nsmgr/issues/675
 
 [See more details](https://github.com/networkservicemesh/sdk/issues/1620)
@@ -110,6 +117,13 @@ Status: RESOLVED.
 [See more details](https://github.com/networkservicemesh/cmd-nsmgr/issues/689)
 
 
+### Fix failed packet tests CI
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/integration-k8s-packet/issues/408)
+
+
 ### Stabilize CI for release/v1.13.2-rc.1
 
 Status: RESOLVED.
@@ -124,13 +138,48 @@ Status: RESOLVED.
 [See more details](https://github.com/networkservicemesh/cmd-forwarder-vpp/issues/1134)
 
 
+### etcd Find seems unreliable when watch is enabled
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/sdk-k8s/issues/512)
+
+
+### failed to delete a NetworkServiceEndpoints
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/cmd-registry-k8s/issues/467)
+
+
+### NSMgr registry streams could leak
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/sdk/issues/1660)
+
+
+### Fix critical CVEs for releases v1.14.0 v1.14.1
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/deployments-k8s/issues/12283)
+
+
 ### Faulty behavior of forwarder-vpp blocks the heal process
 
 Status: RESOLVED.
 
 [See more details](https://github.com/networkservicemesh/cmd-forwarder-vpp/issues/1161)
 
 
+### Memory jump in high-load scenario with nsc/nse release/v1.11.2+
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/cmd-nsmgr/issues/703)
+
+
 
 ## Release project board