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
Currently the IPFIX exporter in FLP is very tied to the Agent/protobuf input and could crash when used in a different context, due to the assumptions done when casting elements from GenericMap.
It is also tied to the configuration defined in the operator, for instance assuming k8s fields are prefixed with "SrcK8S_" or "DstK8S_", which shouldn't be hard-coded.
It should be made more generic.
Here's an example that today doesn't work:
Start a first FLP that reads from IPFIX and write to stdout, using this stdout.yaml:
Currently the IPFIX exporter in FLP is very tied to the Agent/protobuf input and could crash when used in a different context, due to the assumptions done when casting elements from
GenericMap
.It is also tied to the configuration defined in the operator, for instance assuming k8s fields are prefixed with "SrcK8S_" or "DstK8S_", which shouldn't be hard-coded.
It should be made more generic.
Here's an example that today doesn't work:
stdout.yaml
:ipfix-relay.yaml
=>
You'll get errors like:
.. because of the assumptions about types in GenericMap
The text was updated successfully, but these errors were encountered: