You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of this upgrade, we make the following changes:
* Switch to buffered IPFIX exporter in the Flow Aggregator. This
exporter has better performance for UDP IPFIX messages, by ensuring
that multiple data records can be batched together in a single
message.
* Provide Path MTU (PMTU) when creating the IPFIX exporter in the Flow
Aggregator. The value is used by the new buffered exporter to
determine how many IPFIX records can fit in a single message while
avoiding IP fragmentation. In our case, we "approximate" the Path MTU
by looking up the MTU of the Flow Aggregator Pod's eth0 interface.
* Add a MaxMsgSize configuration parameter to the Flow Aggregator as a
way to override the default behavior, which is to use the MTU (minus
header overhead) when the UDP protocol is used.
* Add periodic flushing when exporting IPFIX records, which is necessary
after switching to the buffered exporter. In Aggregation mode,
flushing happens after processing a given batch of expired records. In
Proxy mode, flushing happens every second.
* Use updated reference IPFIX collector in e2e tests. The updated
collector handles the case where multiple data records are included in
the same IPFIX message more gracefully, which leads to some
simplification in the test code.
Signed-off-by: Antonin Bas <[email protected]>
Copy file name to clipboardexpand all lines: build/charts/flow-aggregator/README.md
+1
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,7 @@ Kubernetes: `>= 1.19.0-0`
34
34
| flowAggregatorAddress | string |`""`| Provide an extra DNS name or IP address of flow aggregator for generating TLS certificate. |
35
35
| flowCollector.address | string |`""`| Provide the flow collector address as string with format <IP>:<port>[:<proto>], where proto is tcp or udp. If no L4 transport proto is given, we consider tcp as default. |
36
36
| flowCollector.enable | bool |`false`| Determine whether to enable exporting flow records to external flow collector. |
37
+
| flowCollector.maxIPFIXMsgSize | int |`0`| Maximum message size to use for IPFIX records. If set to 0 (recommended), a reasonable default value will be used based on the protocol (tcp or udp) used to connect to the collector. Min valid value is 512 and max valid value is 65535. |
37
38
| flowCollector.observationDomainID | string |`""`| Provide the 32-bit Observation Domain ID which will uniquely identify this instance of the flow aggregator to an external flow collector. If omitted, an Observation Domain ID will be generated from the persistent cluster UUID generated by Antrea. |
38
39
| flowCollector.recordFormat | string |`"IPFIX"`| Provide format for records sent to the configured flow collector. Supported formats are IPFIX and JSON. |
39
40
| flowCollector.templateRefreshTimeout | string |`"600s"`| Template retransmission interval when using the udp protocol to export records. The value must be provided as a duration string. Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". |
0 commit comments