In [elastic-agent-standalone-kubernetes.yaml](https://github.com/elastic/beats/blob/master/deploy/kubernetes/elastic-agent-standalone-kubernetes.yaml#L217) we suggest `logfile` input for collecting container logs. We should replace it with [Filestream](https://www.elastic.co/guide/en/beats/filebeat/master/filebeat-input-filestream.html) type which brings [many improvements](https://www.elastic.co/blog/read-active-log-files-more-quickly-and-easily-with-the-new-filestream-input-in-filebeat?ultron). With filestream input CRI parsing is also supported by default with the use of [container parser ](https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-input-filestream.html#_container) This has already be done in container-logs integration with this [PR](https://github.com/elastic/integrations/pull/2139)