How can MW developers access the output of currently-runinng (or recently-completed) scheduled maintenance scripts that execute in Kubernetes?

Today this works via journalctl on mwmaint hosts. https://wikitech.wikimedia.org/wiki/Maintenance_server#Access_recent_runs

This question is related to T285896, which could potentially solve this by accessing it via Logstash. Ideally there'd still be a way to do it from the command-line as this would allow for real-time tailing, and easier grepping (Logstash is fairly hostile to simple search ops on small quantities of logs).

\cc @RLazarus

Script output is visible through kubectl logs, and mwscript-k8s can be invoked with -f to immediately start tailing the script output (under the hood, it just invokes that kubectl command). If you don't launch with -f it prints out the kubectl command so you can copy and paste it.

We'll eventually send it to logstash too, but that hasn't happened yet.

In T341560#9967304, @RLazarus wrote:

We'll eventually send it to logstash too, but that hasn't happened yet.

Everything a container produces on stdout and stderr should land in logstash automatically

I’m not sure if it should be a subtask of this or not, but if we’re planning to sunset the mwmaint servers, see also: T384764: mwgrep cannot be used from a deployment host