Support using the container standard output as input for the LogProxyConsumer

[arturo-seijas]

Enhancement Proposal

Currently, log filenames need to be specified for the LogProxyConsumer to be able to scrap them. It would be nice to support gathering the logs from the containers' standard output, which would be beneficial in several ways:

• No need to manage rotation of the logs files
• Reduced risk of losing entries in case a container stops between the write and the scraping of the file
• Logs could be queried without the logging infrastructure without additional tooling, just by using kubectl
• It's the de facto standard

[jnsgruk]

This will likely be very easy for us to support once pebble lands its new log forwarding feature :)

[simskij]

This is exactly what the Pebble Log Forwarding feature aims to solve. Closing this in favor of canonical/pebble#256