Package podlogs enables live capturing of all events and log
messages for some or all pods in a namespace as they get generated.
This helps debugging both a running test (what is currently going
on?) and the output of a CI run (events appear in chronological
order and output that normally isn't available like the command
stdout messages are available).
CopyAllLogs follows the logs of all containers in all pods,
including those that get created in the future, and writes each log
line as configured in the output options. It does that until the
context is done or until an error occurs.
Beware that there is currently no way to force log collection
before removing pods, which means that there is a known race
between "stop pod" and "collecting log entries". The alternative
would be a blocking function with collects logs from all currently
running pods, but that then would have the disadvantage that
already deleted pods aren't covered.
type LogOutput struct {
// If not nil, errors will be logged here. StatusWriter io.Writer// If not nil, all output goes to this writer with "<pod>/<container>:" as prefix. LogWriter io.Writer// Base directory for one log file per container.// The full path of each log file will be <log path prefix><pod>-<container>.log.
LogPathPrefix string
}
LogOutput determines where output from CopyAllLogs goes.