-
Notifications
You must be signed in to change notification settings - Fork 24
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
NETOBSERV-341 configure netflow v5 separately (breaking change if using v5) #207
Conversation
Codecov Report
@@ Coverage Diff @@
## main #207 +/- ##
==========================================
- Coverage 58.16% 57.78% -0.38%
==========================================
Files 58 58
Lines 3361 3364 +3
==========================================
- Hits 1955 1944 -11
- Misses 1276 1289 +13
- Partials 130 131 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
@jotak I reviews the PR and it looks clean to me and can be merged. I think that this is better to be restrictive here, so totally ok with that. BUT:: Merging this PR will break both FLP and NOO testing/deployment over kind:: Need to add the legacy port here: So that this will work with the Netflow simulator A similar thing will happen also to NOO: In https://github.com/netobserv/network-observability-operator/blob/main/.mk/local.mk#L34 We will not expose port 2056 anymore so need to add that to the Operator code ??? |
@eranra thanks, good catches. I've updated the confgen, see the second commit. About the netobserv operator, we can talk about that, but it's not supposed to support netflow v5, we only support ipfix, so I'd rather remove the v5 stuff that is used in make targets, rather than updating the code to handle non-supported v5 |
Looks good, LGTM ... :-) As for the e2e tests ... I looked and we are not really using the simulator in the tests ... just in https://github.com/netobserv/flowogs-pipeline/blob/main/Makefile#L253 so actually this does call for better e2e tests ... we might decide to do that just in the level of NOO and not in FLP ... need to decide. |
Thanks Eran |
Fixes #200
@eranra @KalmanMeth
Is it ok with you to have a breaking changes here? (people who used legacy v5 now have to configure it explicitly)
If that's a problem, we could default to the previous behaviour (legacy port = main port +1) and have another setting to disable v5, but I think it's more simple to keep default as 0 = legacy disabled.