-
Notifications
You must be signed in to change notification settings - Fork 1.7k
--tail No Longer Works in Deploy Mode #2981
New issue
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
Comments
I found the bug - here's a sketch of the solution: #2987 |
@balopat would you still like me to compile a custom version and test this? It seems like you already wrote the tests and merged it. |
Fixes GoogleContainerTools#2981 Signed-off-by: David Gageot <[email protected]>
@cliffburdick I've just built this one from commit 3907a07: sha256: aa46eb3d4e625618e7165f8135540421449f76a97f279597cc35957aacd94231 |
@cliffburdick we had to revert the fix for #1753 because it created other bigger issues |
@dgageot thanks for the update |
This is now working on master
|
I was previously running v0.20.0, and running the following command:
skaffold-0.20.0 deploy --tail -f skaffold-96eb58.yaml --images myimage:1.0
This worked fine, and the logs would tail properly, except for this bug: #1753
In that thread it was mentioned that 0.39.0 fixes this, so I tried it. Now, --tail no longer gives any output, even though I can see it in kubectl log. I'm also not sure if I should see a kubectl process showing the tailed logs, but I don't see those.
Expected behavior
Logs are tailed
Actual behavior
No logs visible
Information
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: