This repository has been archived by the owner on Feb 15, 2023. It is now read-only.
NETOBSERV-184: decouple components into a pipeline #28
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As a previous step for NETOBSERV-184 (Split and Integrate flowlogs2metrics in
kube-enricher), this PR provides an asynchronous pipeline and wraps the current
components into the following roles:
This is only a previous step of the above task to avoid having too large PRs.
The following PRs will try to simplify and decouple even more some existing
components (e.g. Goflow-Kube), remove duplicities. After that, we will
make the Pipeline object to evolve to accomodate the new functionalities
from flowlogs2metrics