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
Apologies if I have misunderstood something.
Presently, bess config in the k8s directory is:
containers: - name: bess image: nimbess/bess
And nimbess is: - name: nimbess-agent image: nimbess/nimbess-agent command: ["/nimbess-agent"]
Unless I am missing something they both need an extra shared mount to exchange information via unix-domain sockets as used in the bess UnixSocketPort?
The text was updated successfully, but these errors were encountered:
I think you are right once we move to unix socket. Right now it's all TCP. See: https://github.com/nimbess/nimbess-agent/blob/master/pkg/drivers/bess/bess.go#L61
We can keep this issue open for tracking the fix for using unix socket instead.
Sorry, something went wrong.
No branches or pull requests
Apologies if I have misunderstood something.
Presently, bess config in the k8s directory is:
And nimbess is:
- name: nimbess-agent
image: nimbess/nimbess-agent
command: ["/nimbess-agent"]
Unless I am missing something they both need an extra shared mount to exchange information via unix-domain sockets as used in the bess UnixSocketPort?
The text was updated successfully, but these errors were encountered: