Sync notes manyally

Signed-off-by: denis-tingaikin <[email protected]>
networkservicemesh · Jan 25, 2024 · 439689b · 439689b
1 parent d087262
commit 439689b
Show file tree

Hide file tree

Showing 3 changed files with 301 additions and 15 deletions.
diff --git a/content/docs/releases/v1.10.0.md b/content/docs/releases/v1.10.0.md
@@ -142,6 +142,15 @@ Counters are more appropriate for NSM data-path metrics instead of histogram.
 [See more details](https://github.com/networkservicemesh/sdk/issues/1464)
 
 
+### Automatically sync-up NSM Site
+
+NSM site is not up to date.
+
+TODO: Consider Hugo modules, which would allow us to ‘import’ docs from repos into site.
+
+[See more details](https://github.com/networkservicemesh/site/issues/251)
+
+
 ### Replace govpp from nsm vpp appss to nsm/govpp
 
 In NSM it's super important to use latest patches or be able to quickly fix some issues in vpp. By this reason we need to start use govpp from nsm organization that improves control of the vpp components in the project.

diff --git a/content/docs/releases/v1.11.0.md b/content/docs/releases/v1.11.0.md
@@ -19,26 +19,52 @@ NSM v1.11.0 has been tested on:
 
 ## Changes since last release
 
+
+
+### Run integration tests in parallel
+
+We need to run the rest of integration tests in parallel
+
+[See more details](https://github.com/networkservicemesh/integration-tests/issues/2862)
+
+
 ### Add LoadBalancer for vl3 networks
 
-NSM vl3 could be perceived as an alternative to k8s networks. Currently, k8s service is the most useful thing in the k8s network.
+NSM vl3 could be perceived as alternative of k8s networks. Currently, k8s service is most useful thing in k8s network. 
 
-At this moment, NSM vl3 network doesn't provide any alternative to k8s services. So we need to consider and implement the best solution for it.
+At this moment, NSM vl3 netowk doesn't provide any alternative of k8s services. So we need to consider and implement the best solution for it.
 
 [See more details](https://github.com/networkservicemesh/deployments-k8s/issues/9210)
 
-### 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.
+### Automatically sync-up NSM Site
+
+NSM site is not up to date.
+
+TODO: Consider Hugo modules, which would allow us to ‘import’ docs from repos into site.
+
+[See more details](https://github.com/networkservicemesh/site/issues/251)
+
+
+### Update vpp version
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/govpp/issues/9)
 
-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
 
+### 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
+
 We need to check scenarios from single cluster testing in multicluster scenarios.
 
 [See more details](https://github.com/networkservicemesh/deployments-k8s/issues/9647)
@@ -55,6 +81,52 @@ We'd added datapath checks for kernel ifaces. https://github.com/networkservicem
 
 
 
+### Update Spire version in Dockerfile for all cmd-repos
+
+
+Update Spire version in Dockerfiles for all cmd-repos. Also add support for multi-arch build.
+
+[See more details](https://github.com/networkservicemesh/cmd-template/issues/123)
+
+
+### `begin` can't do `Unregister` requests without `Register` requests
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/sdk/issues/1515)
+
+
+### Registry k8s can not correctly handle unregister when its scaled
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/sdk-k8s/issues/456)
+
+
+### Parallel SDK testing
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/sdk/issues/1491)
+
+
+### Add VPP config for ARM
+
+
+
+Add vpp config for ARM. The config will be the same as in this PR - https://github.com/networkservicemesh/cmd-forwarder-vpp/pull/905
+
+
+[See more details](https://github.com/networkservicemesh/vpphelper/issues/1)
+
+
+### Update all cmd-*-vpp repos that use edwarnicke/vpphelper
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/vpphelper/issues/4)
+
+
 ### No artifacts after CI run on public clusters
 
 Status: RESOLVED.
@@ -64,9 +136,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)
@@ -81,7 +153,7 @@ Status: RESOLVED.
 
 ### IPSec takes a lot of time on request
 
-Our current implementation uses IKEv2 which requires an `rsa` key. 
+Our current implementation uses IKEv2 which requires an `rsa` key. 
 The thing is the key generation takes about 3-5s - https://github.com/networkservicemesh/sdk-vpp/blob/main/pkg/networkservice/mechanisms/ipsec/common.go
 
 [See more details](https://github.com/networkservicemesh/sdk-vpp/issues/745)
@@ -94,6 +166,14 @@ Status: RESOLVED.
 [See more details](https://github.com/networkservicemesh/deployments-k8s/issues/9864)
 
 
+### AF_PACKET stopped receiving traffic
+
+https://jira.fd.io/browse/VPP-2081
+This issues is a continuation of this discussion - https://github.com/networkservicemesh/govpp/issues/9
+
+[See more details](https://github.com/networkservicemesh/cmd-forwarder-vpp/issues/927)
+
+
 ### Feature Request: Allow configuration of initContainer resource requests and limits
 
 Status: RESOLVED.
@@ -115,6 +195,13 @@ Status: RESOLVED.
 [See more details](https://github.com/networkservicemesh/integration-tests/issues/1667)
 
 
+### Feature Request: Support configuration of NamespaceSelector
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/cmd-admission-webhook-k8s/issues/291)
+
+
 ### Allow setting of registration url via env variable
 
 Status: RESOLVED.

diff --git a/content/docs/releases/v1.12.0.md b/content/docs/releases/v1.12.0.md
@@ -0,0 +1,190 @@
+
++++
+short="v1.12.0"
+title = "Release v1.12.0"
+date="2024-01-24 00:00:00 +0000 UTC"
++++
+
+
+# NSM Release v1.12.0 
+
+
+NSM v1.12.0 has been tested on:
+- [kind](https://github.com/networkservicemesh/integration-k8s-kind/actions?query=branch%3Arelease%2Fv1.12.0+)
+- [GKE](https://github.com/networkservicemesh/integration-k8s-gke/actions?query=branch%3Arelease%2Fv1.12.0+)
+- [AKS](https://github.com/networkservicemesh/integration-k8s-aks/actions?query=branch%3Arelease%2Fv1.12.0+)
+- [AWS/AWS IPv6](https://github.com/networkservicemesh/integration-k8s-aws/actions?query=branch%3Arelease%2Fv1.12.0+)
+- [Bare metal in Equinix Metal](https://github.com/networkservicemesh/integration-k8s-packet/actions?query=branch%3Arelease%2Fv1.12.0+)
+- [Interdomain GKE/AWS/AKS](https://github.com/networkservicemesh/integration-interdomain-k8s/actions?query=branch%3Arelease%2Fv1.12.0+)
+
+## Changes since last release
+
+
+
+### Registry k8s can not correctly handle unregister when its scaled
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/sdk-k8s/issues/456)
+
+
+### Update Spire version in Dockerfile for all cmd-repos
+
+
+Update Spire version in Dockerfiles for all cmd-repos. Also add support for multi-arch build.
+
+[See more details](https://github.com/networkservicemesh/cmd-template/issues/123)
+
+
+## System stability fixes and improvements
+
+
+
+### Interdomain doesn't work when cluster internal IP doesn't have internet access
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/deployments-k8s/issues/10021)
+
+
+### Feature Request: Support configuration of NamespaceSelector
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/cmd-admission-webhook-k8s/issues/291)
+
+
+### Connectivity changes during runtime
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/cmd-nsmgr/issues/89)
+
+
+### 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
+
+
+[See more details](https://github.com/networkservicemesh/deployments-k8s/issues/10726)
+
+
+### Describe how each component interacts with each other
+
+
+For new users, it is unclear how NSM components interact with each other, or how NSM works as a whole.
+For example, how the data packets sent by nsc are passed to nse through forwarder, so that users can have a clear understanding of nsm macroscopically
+
+[See more details](https://github.com/networkservicemesh/site/issues/262)
+
+
+### TestRecvfd/TestRecvfdClosesSingleFile is unstable
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/sdk/issues/1525)
+
+
+### Broken "cloud.google.com/go/compute/metadata" dependency
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/sdk/issues/1551)
+
+
+### CVEs Scanner should merge the same CVEs
+
+Currently, CVEs Scanner creates several entries for the same CVE if it's found in different images. The scanner should merge such entires into one and add all affected images into the entry's description.
+
+[See more details](https://github.com/networkservicemesh/deployments-k8s/issues/10810)
+
+
+### Fix `CRITICAL` and `HIGH` issues from CVEs scanner
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/deployments-k8s/issues/10770)
+
+
+### Add interface names into NSM metrics 
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/sdk-vpp/issues/768)
+
+
+### Test_DNSUsecase is unstable
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/sdk/issues/1537)
+
+
+### Update repository to go v1.20
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/cmd-csi-driver/issues/25)
+
+
+### Test_TCPDNSServerTimeout is unstable
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/sdk/issues/1532)
+
+
+### Example TestNsm_kuma_universal_vl3 is unstable on kind
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/deployments-k8s/issues/10140)
+
+
+### Remaining bridge interfaces after forwarder stoped
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/sdk-ovs/issues/276)
+
+
+### About nsm support network topology like this?
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/deployments-k8s/issues/10519)
+
+
+### Feature: automatic nsc connect to nse registered with the NS after nsc is initialized and running
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/deployments-k8s/issues/9889)
+
+
+###  Visualizing tool for NSM in Kubernetes environment 
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/deployments-k8s/issues/10648)
+
+
+### rate: Wait(n=1) would exceed context deadline
+
+
+Logs: 
+```
+{"level":"error","ts":1705506855.7787008,"logger":"admissionWebhookServer","caller":"build/main.go:97","msg":"failed to get namespace by name: client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline","stacktrace":"main.(*admissionWebhookServer).Review\n\t/build/main.go:97\nmain.main.func3\n\t/build/main.go:482\ngithub.com/labstack/echo/v4.(*Echo).add.func1\n\t/go/pkg/mod/github.com/labstack/echo/[email protected]/echo.go:582\ngithub.com/labstack/echo/v4/middleware.RecoverWithConfig.func1.1\n\t/go/pkg/mod/github.com/labstack/echo/[email protected]/middleware/recover.go:131\ngithub.com/labstack/echo/v4/middleware.LoggerWithConfig.func2.1\n\t/go/pkg/mod/github.com/labstack/echo/[email protected]/middleware/logger.go:126\ngithub.com/labstack/echo/v4.(*Echo).ServeHTTP\n\t/go/pkg/mod/github.com/labstack/echo/[email protected]/echo.go:669\nnet/http.serverHandler.ServeHTTP\n\t/usr/local/go/src/net/http/server.go:2936\nnet/http.(*conn).serve\n\t/usr/local/go/src/net/http/server.go:1995"}
+```
+Build: https://github.com/networkservicemesh/integration-k8s-kind/actions/runs/7558182942/job/20579105121
+
+[See more details](https://github.com/networkservicemesh/cmd-admission-webhook-k8s/issues/384)
+
+
+
+## Release project board
+
+[Notes based on](https://github.com/orgs/networkservicemesh/projects/22)