-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
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
WIP: evebox agent support #32
base: master
Are you sure you want to change the base?
Conversation
… and evebox-server for kind deployments
vars: | ||
# more specific is better for alert accuracy and performance | ||
address-groups: | ||
HOME_NET: "[192.168.0.0/16,10.0.0.0/8,172.16.0.0/12]" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could this be filled with internal prefixes + trusted networks?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This another example of how we spread configurations between metal-networker and firewall-controller. This file is written by metal-networker, so actually no possibility to access these variables.
This file is only a example deployment for local development in kind. We need to think about a easier solution here.
compiles but untested, changes to gepm not implemented yet, wait for review comments on this implementation before starting gepm pr.