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

The output of "kubectl get taskruns" was really confusing #717

Closed
vincent-pli opened this issue Apr 4, 2019 · 1 comment
Closed

The output of "kubectl get taskruns" was really confusing #717

vincent-pli opened this issue Apr 4, 2019 · 1 comment
Assignees
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.

Comments

@vincent-pli
Copy link
Member

Expected Behavior

When I execute kubectl get taskruns, I expect to get a clear and helpful information.
These information could tell me the status of taskruns at least.

A simple one should look like this:

NAME      AGE      STATUS
test-run   1h         Running

A better one like this:

NAME      AGE      STEPS      STATUS    REASON
test-run   1h     1/3          Running         -

Actual Behavior

NAME      TYPE        STATUS   STARTTIME   COMPLETIONTIME
test-run   Succeeded   False        1d                1d

This output seems like the "Pod condition" ? The "False/True" things. I think it's not make sense to display these information here.

Additional Info

I also check the Argo's "workflow" the same thing with "taskrun", the output like this:

kubectl -n kubeflow get workflow
NAME                         AGE
calculation-pipeline-drllv   15d

But in the output of kubectl get taskruns -o yaml, I get this:

  phase: Succeeded
  startedAt: 2019-03-19T06:37:23Z

So I suggest add phase to the status section of taskrun and display as STATUS in the output of kubectl get taskruns if needed.

@vdemeester vdemeester added kind/feature Categorizes issue or PR as related to a new feature. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Apr 5, 2019
@vdemeester
Copy link
Member

/assign @vincent-pli

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants