-
Notifications
You must be signed in to change notification settings - Fork 1
Persist Logs of e2e Tests #48
Copy link
Copy link
Open
Labels
Q2/2026This topic is relevant for the hackathon in Q2/2026.This topic is relevant for the hackathon in Q2/2026.area/dev-productivityDeveloper productivity related (how to improve development)Developer productivity related (how to improve development)kind/enhancementEnhancement, improvement, extensionEnhancement, improvement, extensionlifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.teamsize/mediumA team of 3 people.A team of 3 people.
Description
Metadata
Metadata
Assignees
Labels
Q2/2026This topic is relevant for the hackathon in Q2/2026.This topic is relevant for the hackathon in Q2/2026.area/dev-productivityDeveloper productivity related (how to improve development)Developer productivity related (how to improve development)kind/enhancementEnhancement, improvement, extensionEnhancement, improvement, extensionlifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.teamsize/mediumA team of 3 people.A team of 3 people.
Type
Fields
Give feedbackNo fields configured for issues without a type.
How to categorize this topic?
/area dev-productivity
/kind enhancement
/label teamsize/medium
What is the topic about?:
Gardener e2e tests export the logs of running pods/machines before exiting – both on success and failure – so that they can be viewed/downloaded in the artifacts browser (gcsweb).
However, logs of terminated pods/machines will not be exported if they are not running at the end of the test execution. I.e., we don't collect logs of pods/machines of successful test cases, because the shoots will be deleted as part of the test execution.
Debugging e2e test failures based on this information is very tedious. The ability to search e2e test logs or to compare logs of successful/tailed tests would improve this experience.
For this, we could add a logging stack to the Prow cluster (similar to the performance prometheus) where e2e test logs are stored and which can be queried in the cluster's Plutono instance.