And basically will run on every worker note and it will collect the log data that containers are producing,
it will process this data, it will enrich the log data like at a time stamp to it at the source, like
which part produced the log, et cetera, and then send these prepared and processed log data to a Lustick
two story.
So as the next step, we're going to deploy fluent in our cluster.
And as I mentioned, fluency is going to run on every worker node and there's a special component in
coronaries that by default makes that application run on every worker node without additional configuration.
So you don't have to set a number of replicas.
It basically knows if you add a new worker node, it will start the EP there automatically.
You don't have to do anything manually.
And that component in communities is called Deman Set.
So as a next step, we're going to deploy fluently, Deman said in our cluster.