-
## Overview
Currently the log level can be configured via environment variable `NSM_LOG_LEVEL` which means the process will use the configured value for its whole lifetime. It is fine in most of th…
-
Steps to reproduce:
Configure envs on endpoint
```
- name: NSM_IPAM_POLICY
value: strict
- name: NSM_CIDR_PREFIX
value: 172.16.1.100/27,2001:db8::/116
```
…
-
Probably related to this fix: https://github.com/networkservicemesh/integration-tests/pull/2692
### Incidents
https://github.com/networkservicemesh/integration-k8s-kind/actions/runs/4789367878
https…
-
## Expected Behavior
Network service name specified with cluster name should work both in remote clusters and in the same cluster where the service is located.
## Current Behavior
If …
-
## Links
- https://github.com/networkservicemesh/integration-k8s-gke/actions/runs/5619508780
- https://github.com/networkservicemesh/integration-k8s-aws/actions/runs/5657007438
- https://github.com/n…
-
## Expected Behavior
Latency should be consistent, regardless of the type of interface.
## Current Behavior
When using memif mechanism there are occasional latency spikes.
See my comment for m…
-
## Expected Behavior
Installing NSM with helm3 from networkservicemesh/deployments/helm/nsm should render a working NSM system.
## Current Behavior
The installation fails with error, that…
-
## Expected Behavior
If a Kubernetes node hosting NSEs is lost or restarted, the NSE registrations (`networkserviceendpoint` CR instances) get removed from the NSM registry.
## Current Behavio…
-
## Motivation
currently, we are using rest calls always https://github.com/networkservicemesh/integration-k8s-aks/blob/main/scripts/aks-start.sh#L57
For this reason, sometimes we see this on CI
http…
-
## Expected Behavior
I would like to change the endpoint composition by adding a new pod in the middle of the chain, by simply modifying the network service definition file.
## Actual Behavior
A…