We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NSMgr becomes available by unix socket and by TCP socket in almost the same time.
It can take up to 30s between NSMgr becomes available by unix socket and by TCP socket.
30s
deployments-k8s commit : 5ac6b19cde16ae2c83eb4bc0cb213e1097ab9a16. Failed test - TestRemote_nsmgr_restart https://github.com/networkservicemesh/integration-k8s-gke/runs/3438417489
deployments-k8s
TestRemote_nsmgr_restart
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Expected behavior
NSMgr becomes available by unix socket and by TCP socket in almost the same time.
Current behavior
It can take up to
30s
between NSMgr becomes available by unix socket and by TCP socket.Build details
deployments-k8s
commit : 5ac6b19cde16ae2c83eb4bc0cb213e1097ab9a16.Failed test -
TestRemote_nsmgr_restart
https://github.com/networkservicemesh/integration-k8s-gke/runs/3438417489
The text was updated successfully, but these errors were encountered: