-
Notifications
You must be signed in to change notification settings - Fork 267
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
Update how we identify the correct pod to use for logs #843
Comments
/assign |
fyi, no rush on this one currently as the change in pipelines was reverted due to a regression it caused for retries. |
Ok, in that case I'm going to unassign myself since there's more urgent work I'm currently doing |
Not currently needed, we can reopen if this changes in a future pipelines version. |
Looks like this is being revisited |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
/remove-lifecycle stale |
Putting this one on ice for now as there are no immediate plans to remove the pod name. |
Closing since there's no sign of this changing anytime soon. We can reopen if needed. |
See tektoncd/pipeline#1689 and associated PR for details.
TL;DR:
.status.podName
may be removed in future. We should consider updating our strategy to identify the correct pod, i.e. by usinglabelSelector
withtekton.dev/taskRun={taskRunName}
.The text was updated successfully, but these errors were encountered: