Expected Behavior
There are some re-tries in management of annotations using Server-Side Apply patch when TaskRuns in a PipelineRun are executed sequentially (using runAfter). The following warning is logged: .* due to Server-Side Apply patch conflict, using force patch.. The issue is not observed when TaskRuns are executed in parallel (runAfter is not used). The issue was easy to reproduce in a local Kind environment, a PipelineRun with 5 TaskRuns with a light payload (echo "something").
Actual Behavior
Steps to Reproduce the Problem
Additional Info
Expected Behavior
There are some re-tries in management of annotations using Server-Side Apply patch when TaskRuns in a PipelineRun are executed sequentially (using runAfter). The following warning is logged:
.* due to Server-Side Apply patch conflict, using force patch.. The issue is not observed when TaskRuns are executed in parallel (runAfter is not used). The issue was easy to reproduce in a local Kind environment, a PipelineRun with 5 TaskRuns with a light payload (echo "something").Actual Behavior
Steps to Reproduce the Problem
Additional Info
Kubernetes version:
Output of
kubectl version:Tekton Pipeline version:
Output of
tkn versionorkubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'