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

Hard to find stdout #44

Open
iskandr opened this issue Sep 12, 2016 · 2 comments
Open

Hard to find stdout #44

iskandr opened this issue Sep 12, 2016 · 2 comments

Comments

@iskandr
Copy link
Member

iskandr commented Sep 12, 2016

Find the standard out for a workflow seems to currently require opening the root node of the workflow, clicking "Backend details/queries" and then clicking "kubectl-logs". The process is overall cumbersome and "kubectl-log" seems particularly opaque. Why can't there just be "stdout" and "stderr" links associated with a workflow?

@smondet
Copy link
Member

smondet commented Sep 12, 2016

That's what Kubernetes gives us (kubectl logs doesn't give the distinction).

@hammer
Copy link
Member

hammer commented Sep 12, 2016

Wow I'm surprised that kube mixes stdout and stderr! Please vote at kubernetes/kubernetes#28167 and hopefully they'll fix that soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants