kubernetes/cluster/log-dump
David Porter 0ec1530e41 log grabbing: obtain timestamps on extra services
Previously if any test jobs added additional log dumps, such as
`containerd-installation` for example, the logs would grabbed with `sudo
journalctl --output=cat`. `--output=cat` excludes timestamps which
makes debugging difficult. Let's use `short-precise` output similar to
to the other log grabbing commands which includes timestamps.

Signed-off-by: David Porter <david@porter.me>
2022-02-10 16:44:31 -08:00
..
log-dump.sh log grabbing: obtain timestamps on extra services 2022-02-10 16:44:31 -08:00
logexporter-daemonset.yaml Enable per-zone logexporter pods creation 2020-09-25 15:45:49 +02:00
OWNERS Check in OWNERS modified by update-yamlfmt.sh 2021-12-09 21:31:26 -05:00
README.md Make log-dump's deprecation note up-to-date 2020-12-15 09:58:09 +01:00

This directory is deprecated!

Log dumping utility was ported from kubernetes/kubernetes repository to kubernetes/test-infra. If you require changes to this script, please consider migrating your jobs to use the new log dumping mechanism first.

Currently, log-dump.sh file is added to every newly released kubekins-e2e image. In order to leverage that script, add USE_TEST_INFRA_LOG_DUMPING environment variable to your test job and set its value to true.

Migration steps

For the time being, only GCE and GKE providers are supported by the log-dump mechanism. To make the mechanism support your Kubernetes provider in tests using kubekins-e2e, modify the logDumpPath function in kubetest to handle your provider and adapt log-dump.sh in accord to your needs.