-
## Steps to reproduce
1. Create NSC that sets the kernel local mechanism in the request.Connection.Mechanism.
2. Deploy nsmgr, forwarder, nsc, nse
Actual: NSC cannot connect to NSE.
Expected:…
-
## Expected Behavior
The generic NSM frameworks shall not have any dependency towards a specific data-plane.
It should be possible to use NSM for networks/endpoints/services, possibly own-develo…
-
## Expected Behavior
`cmd-forwarder-vpp` shouldn't reach memory limit during tests.
## Current Behavior
`cmd-forwarder-vpp` reaches current memory limit (400Mi) during basic, heal tests on packet…
-
## Problem statement
If test failed on ci we can not get logs from nsm components.
## Solution
Always write logs into memory logger.
If `t.Failed()` then push all logs into stdout.
##…
-
Good morning:
When following the instructions on simple-bridge, the containers become stuck in an Init:0/1 state in kubectl get pods, never reaching the "initialised" state.
The command kubectl…
-
## Overview
Currently, for every client a new gRPC server is created, which might be expensive.
The idea is to serve all requests with a single server using identity from request's SPIRE sertifi…
-
### Description
For various reasons, current standard applications may not meet user requirements. We need to provide a description and instructions how to create a custom endpoint
-
## Description
We can add the `SupportedMechanisms` field into [NetworkServiceEndpoint](https://github.com/networkservicemesh/api/blob/master/pkg/api/registry/registry.proto#L29
) to directly indi…
-
## Link to the Google Docs document
https://docs.google.com/document/d/1HhDYm-uuATFz0xHgJsZ-GQ_9WrXbkKoQkiTxEtYzil0/edit?usp=sharing
## Raw estimation
18d
-
## Overview
As we have our traffic data for pod-to-pod connections, we would like to have a good and interactive way to visualize the topology and see generated traffic.
The inspiration came fro…