The current runPod documentation says that it outputs a single file of /[collector-name]/[collector-name].log. As of https://github.com/replicatedhq/troubleshoot/pull/1172 we also log the output of kubectl describe pod <pod-name spread across two files.
/[collector-name]/[collector-name].json # Pod definition and status
/[collector-name]/[collector-name]-events.json # Pod events
These files are important as they allow users to determine the status of a runPod pod in an analyzer.
Describe the rationale for the suggested feature.
The current
runPoddocumentation says that it outputs a single file of/[collector-name]/[collector-name].log. As of https://github.com/replicatedhq/troubleshoot/pull/1172 we also log the output ofkubectl describe pod <pod-namespread across two files./[collector-name]/[collector-name].json# Pod definition and status/[collector-name]/[collector-name]-events.json# Pod eventsThese files are important as they allow users to determine the status of a
runPodpod in an analyzer.