Show account that created a PipelineRun or TaskRun

[Conky5]

It would be handy when doing a tkn pr describe ... or tkn tr describe ... to see which account started the run.

[danielhelfand]

@Conky5 Could you please describe what you mean by account in this context?

Perhaps even include pseudo output of a tkn pr describe or tkn tr describe with this use case in mind?

[chmouel]

Maybe the serviceaccount? Which we are not showing...

[danielhelfand]

ServiceAccount should be available for both describe commands.

[chmouel]

ah yes sorry, somehow i missed it 😅

[Conky5]

Thanks for the quick responses 😄. By account I mean the account that is authenticated to kubernetes when the run is created. For example if I create a pipeline run and then run a describe I see something like:

$ tkn pr describe example-9zrts
Name:              example-9zrts
Namespace:         example
Pipeline Ref:      example-pipeline
Service Account:   default

🌡️   Status

STARTED        DURATION    STATUS
19 hours ago   4 seconds   Succeeded

📦 Resources

 No resources

⚓ Params

 NAME             VALUE
 ∙ my-parameter

🗂  Taskruns

 NAME                                       TASK NAME   STARTED        DURATION    STATUS
 ∙ example-9zrts-something-wl4lc   something   19 hours ago   4 seconds   Succeeded

Other folks who run a describe like that do not know who started it, let's say conky5@example.com is my account. Pseudo output that includes this information could look like:

$ tkn pr describe example-9zrts
Name:              example-9zrts
Namespace:         example
Pipeline Ref:      example-pipeline
Service Account:   default
User:              conky5@example.com

🌡️   Status

STARTED        DURATION    STATUS
19 hours ago   4 seconds   Succeeded

📦 Resources

 No resources

⚓ Params

 NAME             VALUE
 ∙ my-parameter

🗂  Taskruns

 NAME                                       TASK NAME   STARTED        DURATION    STATUS
 ∙ example-9zrts-something-wl4lc   something   19 hours ago   4 seconds   Succeeded

[danielhelfand]

@Conky5 Thanks for the clarification! I think this makes sense. I am wondering if this would require some work in pipeline as well to capture this data on the PipelineRun/TaskRun? The question would be how to make sure it persists on the created object cause we can definitely capture the user from the CLI.

cc @chmouel @vdemeester

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.