Chitrang Patel
Chitrang Patel
> Thanks @jerop > > Have we done any measurements around the overhead of 1. adding a sidecar to each taskRun that requires a result and 2. having the reconciler...
> > @dibyom I was supposed to do that but I completely missed it. When you say overhead, you just mean in terms of memory and CPU footprint of the...
> @chitrangpatel Thank you so much for the performance benchmarking numbers. The extra 3s overhead to startup time per taskrun is a bit concerning. Wondering - does the latency go...
/assign
I think I was able to recreate this issue with the following yaml: ```yaml apiVersion: tekton.dev/v1beta1 kind: TaskRun metadata: generateName: steps-run-in-order- spec: workspaces: - name: my-workspace emptyDir: {} taskSpec: workspaces:...
WorkingDir is initialized via the [`initContainers`](https://github.com/tektoncd/pipeline/blob/b7c29b485216298935871e6bef52bd31048e6cb5/pkg/pod/pod.go#L175-L177). It is executed before all other steps. So when we specify the `workingDir`, that directory will be created before the first step. And so...
Discussion point since I am probably missing a lot of context here: If one of the steps (could be the last step) wants to use a workingDir, it is created...
/assign @wlynch (@chuangw6 suggested that you might be interested in this PR 🙂 )
/assign @wlynch