-
Notifications
You must be signed in to change notification settings - Fork 366
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
Improve antctl features in flow-aggregator #3642
Improve antctl features in flow-aggregator #3642
Conversation
8cc2899
to
f8453d8
Compare
Codecov Report
@@ Coverage Diff @@
## main #3642 +/- ##
==========================================
- Coverage 49.03% 45.69% -3.35%
==========================================
Files 261 256 -5
Lines 39245 38216 -1029
==========================================
- Hits 19245 17462 -1783
- Misses 18128 18994 +866
+ Partials 1872 1760 -112
Flags with carried forward coverage won't be shown. Click here to find out more.
|
892893a
to
03cc4c6
Compare
03cc4c6
to
a0b1803
Compare
This pull request introduces 1 alert when merging a0b1803 into 2ab80d0 - view on LGTM.com new alerts:
|
a0b1803
to
7eeb50b
Compare
This pull request introduces 1 alert when merging 7eeb50b into 2ab80d0 - view on LGTM.com new alerts:
|
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.
IMO, there is a major issue with this PR: these commands are not troubleshooting commands, there are used to update the FlowAggregator configuration, yet changes made through antctl are not persistent (if the FlowAggregator Pod restarts, these changes will be lost) and they conflict with the "source of truth" that would be the ConfigMap. I don't think that's right, and we had the same issue in the past with the Antrea configuration.
7f49f4f
to
2492701
Compare
3c2b293
to
c257785
Compare
154f29d
to
1317491
Compare
c3d9b00
to
85c1fd5
Compare
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.
a couple more small comments
85c1fd5
to
b9bb280
Compare
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.
LGTM, please squash all your commits into a single one, with a helpful and well-formatted commit message.
b9bb280
to
63a4421
Compare
1. Add “antctl set flow-aggregator” command for antctl in order to update clickhouse/flow-collector related parameters. 2. “antctl set flow-aggregator” will directly mutate the volume configMap of flow-aggregator 3. Mounted ConfigMap will be updated in 1min if there is a modification of volume configMap 4. Create watcher in flow-aggregator pod to watch mounted configMap and let fa pod react to the changes 5. “antctl set flow-aggregator” can only be used in flow-aggregator pod currently. Signed-off-by: Yun-Tang Hsu <hsuy@vmware.com>
63a4421
to
e9dad14
Compare
/test-conformance |
/test-conformance |
Changing clickhouse/flow-collector related parameters at runtime and update configmap.
Enable ClickHouse
$ antctl set flow-aggregator clickHouse.enable=true
Update ClickHouse database
$ antctl set flow-aggregator clickHouse.database=name
Update ClickHouse databaseURL
$ antctl set flow-aggregator clickHouse.databaseURL=http://xxxxx
Update ClickHouse debug
$ antctl set flow-aggregator clickHouse.debug=true
Update ClickHouse compress
$ antctl set flow-aggregator clickHouse.compress=true
Update ClickHouse commitInterval
$ antctl set flow-aggregator clickHouse.commitInterval=10s
Update ClickHouse ttl (unit in second)
$ antctl set flow-aggregator clickHouse.ttl=100
Update IPFIX Flow Collector address
$ antctl set flow-aggregator flowCollector.address=:[:]
Enable IPFIX Flow Collector
$ antctl set flow-aggregator flowCollector.enable=true
Signed-off-by: Yun-Tang Hsu hsuy@vmware.com