Skip to content
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

Following logs, optionally until the job/pod completes #50

Closed
mumoshu opened this issue Mar 9, 2018 · 2 comments
Closed

Following logs, optionally until the job/pod completes #50

mumoshu opened this issue Mar 9, 2018 · 2 comments

Comments

@mumoshu
Copy link
Collaborator

mumoshu commented Mar 9, 2018

Extracted from #49 (comment)

This still seems like a scope-creep regarding what helmfile do today, yet I find nowhere to do this cleanly outside of helmfile.

@mumoshu mumoshu mentioned this issue Mar 9, 2018
@gtaylor
Copy link

gtaylor commented Mar 12, 2018

This does seem like we're probably creeping scope a bit. Hate to see helmfile get to be too hairy/complex.

Might this be more the province of something more heavy-duty like Spinnaker.

@mumoshu
Copy link
Collaborator Author

mumoshu commented Mar 12, 2018

@gtaylor Thank you very much for the feedback!
It really helps shape helmfile's direction and scope.

Honestly saying, I won't agree with calling out Spinnaker just for tailing logs, but I do agree that you would certainly use an another tool for tailing logs like stern!

Perhaps just running stern until the pod/job finishes would do the job today.
Let's close this and keep us concentrated on what helmfile would clearly do.

Thanks again for your feedback 👍

@mumoshu mumoshu closed this as completed Mar 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants