You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Topology aware scale-from-zero running of NSEs in response to NSC demand: Implement a chain element that can produce pod based on the passed template
#141
Method request should produce a pod from the template (2.1) at the node from step 3 via k8s api client. Note: we also need to inject env with NSE labels into producing pod. See at env example: https://github.com/networkservicemesh/cmd-nse-icmp-responder/blob/main/main.go#L74
Default env name: "NSM_LABELS"
Value should be: nodeName: ${node_name_from_request}
Also, we could make the env name configurable.
If step 4 was a success then the chain element should return an error. For example
return resp, errors.New("cannot provide required networkservice")
Note: It is required because we need to make permutation on nsmgr side to select the endpoint that we created on step 4.
6. Add unit tests to cover
Description
We need to implement a chain element that could supply pod on the specific node on Request.
Implementation details
2.1. Pod spec. See the model definition: https://pkg.go.dev/k8s.io/api/core/v1#Pod
2.2. K8s API client interface. See at an example: https://github.com/networkservicemesh/sdk-k8s/blob/main/pkg/registry/etcd/nse_server.go#L145
Default env name: "NSM_LABELS"
Value should be: nodeName: ${node_name_from_request}
Also, we could make the env name configurable.
Note: It is required because we need to make permutation on nsmgr side to select the endpoint that we created on step 4.
6. Add unit tests to cover
References
networkservicemesh/sdk#892
The text was updated successfully, but these errors were encountered: