Add release notes for v1.12.0

.github/sync/Makefile

@@ -1,3 +1,3 @@
-fetch-notes-build:
+pull-release-notes-build:
 	@GOPATH=$(GOPATH) GOBIN=$(GOBIN) go build -o fetchnotes main.go githubv4.go
 	mv fetchnotes ../../bin/fetchnotes

.github/workflows/sync.yaml

@@ -14,7 +14,7 @@ jobs:
         with:
           go-version: 1.20.8
       - name: build & run fetchnotes
-        run: make fetch-notes
+        run: make pull-release-notes
         env:
           GITHUB_TOKEN: ${{ secrets.NSM_BOT_GITHUB_TOKEN }}
       - name: Create commit message

Makefile

@@ -4,10 +4,10 @@ yarn:
 clean:
 	rm -rf public resources
 
-fetch-notes-build: 
+pull-release-notes-build: 
 	$(MAKE) -C .github/sync
 
-fetch-notes: fetch-notes-build
+pull-release-notes: pull-release-notes-build
 	@echo make sure that GITHUB_TOKEN is set
 	@GITHUB_TOKEN=$(GITHUB_TOKEN) bin/fetchnotes
 

content/docs/releases/history.md

@@ -3,6 +3,20 @@ title = "History"
 weight = 2
 +++
 
+## 1.12
+
+**Latest Release:** 1.12.0 (released: 2024-01-24)\
+**Patch Releases:** [1.12.0](../v1.12.0)\
+**Kubernetes support:**  v1.21, v1.22, v1.23, v1.24, v1.25, v1.26, v1.27, v1.28
+
+
+## 1.11
+
+**Latest Release:** 1.11.0 (released: 2023-12-07)\
+**Patch Releases:** [1.11.0](../v1.11.0)\, [1.11.2](../v1.11.2)\
+**Kubernetes support:**  v1.21, v1.22, v1.23, v1.24, v1.25, v1.26, v1.27, v1.28
+
+
 ## 1.10
 
 **Latest Release:** 1.10.0 (released: 2023-07-18)\

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.

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,139 @@ Status: RESOLVED.
 [See more details](https://github.com/networkservicemesh/integration-tests/issues/1667)
 
 
+### Feature Request: Support configuration of NamespaceSelector
+
+
+
+Auto registration creates a `MutatingWebhookConfiguration` with no Namespace filters.
+The mutation applies to all Namespaces.
+
+The Webhook watching the system namespaces can create circular dependencies. Where system pods are required for Nodes to be made Ready to have the Webhook scheduled onto them.
+
+We would like to configure this selector to exclude some Namespaces which should never be modified. 
+For example we could configure the webhook to exclude the namespaces: `nsm-system` `kube-system` and `spire`.
+
+Example of current webhook config:
+
+```
+kind: MutatingWebhookConfiguration
+metadata:
+  name: nsm-admission-webhook-k8s-5dfd78487d-26n5b
+webhooks:
+- admissionReviewVersions:
+  - v1
+  clientConfig:
+    caBundle: <redacted>
+    service:
+      name: admission-webhook-svc
+      namespace: nsm-system
+      path: /mutate
+      port: 443
+  failurePolicy: Fail
+  matchPolicy: Equivalent
+  name: nsm-admission-webhook-k8s-5dfd78487d-26n5b.networkservicemesh.io
+  namespaceSelector: {}
+  objectSelector: {}
+  reinvocationPolicy: Never
+  rules:
+  - apiGroups:
+    - ""
+    apiVersions:
+    - v1
+    operations:
+    - CREATE
+    - UPDATE
+    resources:
+    - pods
+    scope: '*'
+  - apiGroups:
+    - apps
+    apiVersions:
+    - v1
+    operations:
+    - CREATE
+    - UPDATE
+    resources:
+    - deployments
+    - statefulsets
+    - daemonsets
+    - replicasets
+    scope: '*'
+  sideEffects: None
+  timeoutSeconds: 10
+```
+
+Example of desired webhook config:
+
+```
+kind: MutatingWebhookConfiguration
+metadata:
+  name: nsm-admission-webhook-k8s-5dfd78487d-26n5b
+webhooks:
+- admissionReviewVersions:
+  - v1
+  clientConfig:
+    caBundle: <redacted>
+    service:
+      name: admission-webhook-svc
+      namespace: nsm-system
+      path: /mutate
+      port: 443
+  failurePolicy: Fail
+  matchPolicy: Equivalent
+  name: nsm-admission-webhook-k8s-5dfd78487d-26n5b.networkservicemesh.io
+  namespaceSelector:
+    matchExpressions:
+    - key: kubernetes.io/metadata.name
+      operator: NotIn
+      values:
+      - nsm-system
+      - kube-system
+      - spire
+  objectSelector: {}
+  reinvocationPolicy: Never
+  rules:
+  - apiGroups:
+    - ""
+    apiVersions:
+    - v1
+    operations:
+    - CREATE
+    - UPDATE
+    resources:
+    - pods
+    scope: '*'
+  - apiGroups:
+    - apps
+    apiVersions:
+    - v1
+    operations:
+    - CREATE
+    - UPDATE
+    resources:
+    - deployments
+    - statefulsets
+    - daemonsets
+    - replicasets
+    scope: '*'
+  sideEffects: None
+  timeoutSeconds: 10
+  ```
+
+
+
+
+
+
+
+
+
+
+
+
+[See more details](https://github.com/networkservicemesh/cmd-admission-webhook-k8s/issues/291)
+
+
 ### Allow setting of registration url via env variable
 
 Status: RESOLVED.
@@ -174,6 +387,13 @@ Status: RESOLVED.
 [See more details](https://github.com/networkservicemesh/site/issues/256)
 
 
+### missing interface in NSE after relocation
+
+Status: RESOLVED.
+
+[See more details](https://github.com/networkservicemesh/deployments-k8s/issues/9863)
+
+
 ### Automate updating versing of 'go' 
 
 Updating version of 'go' is a very monotonous and most importantly time-consuming task since we need to update all our repositories (https://github.com/networkservicemesh?q=&type=all&language=go&sort= we have 54  repos)