Open jkuma145 opened 5 days ago
Can you share an example of a PipelineRun exhibiting this behaviour? Depending on what it's doing this may be expected.
See https://tekton.dev/docs/pipelines/affinityassistants/
coschedule workspaces - When a PersistentVolumeClaim is used as volume source for a Workspace in a PipelineRun, all TaskRun pods within the PipelineRun that share the Workspace will be scheduled to the same Node. (Note: Only one pvc-backed workspace can be mounted to each TaskRun in this mode.)
coschedule workspaces is the default behaviour, but other options are available including disabling the affinity assistant as described on that page.
If your PipelineRuns are not using a PVC as described, please share more details to help understand and reproduce the behaviour.
Hello I'm running 5 pipelinerun parallely for 5 applications. Pipelineruns -> Taskruns -> Pods which are executing on single node for all 5 pipelinerun. I can understand that single pipelinerun can run multiple task and multiple pods on single node as we are sharing the workspace using coherent. but unexpected behavior is all pipelinerun running all pods on single node only.
attached pod sample
Expected Behavior
For each pipelineruns, Pods should be run on multiple nodes. I'm running 5 pipelinerun parallelly which is running all pods on single nodes. I have 5-6 nodes in my cluster where tekton is hosted.
Actual Behavior
Steps to Reproduce the Problem
Additional Info
1.28.6
Output of
kubectl version
:Tekton Pipeline version:
Output of
tkn version
orkubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'
I'm trying to tekton cluster in HA even, but most of pods are running on single node only.
tektonpipelines