Skip to content
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

Open
wants to merge 27 commits into
base: master
Choose a base branch
from
Open

WIP: evebox agent support #32

wants to merge 27 commits into from

Conversation

majst01
Copy link
Contributor

@majst01 majst01 commented Jun 19, 2020

compiles but untested, changes to gepm not implemented yet, wait for review comments on this implementation before starting gepm pr.

@majst01 majst01 requested a review from mwindower June 19, 2020 13:00
@majst01 majst01 assigned mwindower and unassigned mwindower Jun 19, 2020
controllers/firewall_controller.go Outdated Show resolved Hide resolved
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]"
Copy link
Contributor

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?

Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants