We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When we run the smoke cluster and it fails, we are running without a metrics deployment, so we lose logging.
We should have a second metrics deployment that collects logs from the ci jobs.
The text was updated successfully, but these errors were encountered:
My idea for this was quite simple, have additional GitHub action jobs that just echo the logs
Sorry, something went wrong.
We can already run on the same runner then it's just kubectl
Actually even simpler, we can just have a bg process in the ci job that echoes the logs while the test runs
Maddiaa0
just-mitch
No branches or pull requests
Overview
When we run the smoke cluster and it fails, we are running without a metrics deployment, so we lose logging.
We should have a second metrics deployment that collects logs from the ci jobs.
The text was updated successfully, but these errors were encountered: