<p>Currently I am using <code>Jenkins on kubernetes</code> and wanted to migrate to <code>tekton</code> because trying achieve CI steps as a code (similar to Helm chart for CD steps). Just wondering about Tekton architecture -</p>
<p>why every task creates different pod rather than creating different containers in a single pod. Creating multiples pod leads resources locking as every pod will hold cpus/memory (default) till pod receives SIGTERM.</p>

Ashish Kumar
<blockquote>
<p>Just wondering about Tekton architecture -
why every task creates different pod rather than creating different containers in a single pod?</p>
</blockquote>
<p>This is a design choice that was made early in the project. They want <em>Tasks</em> to be a reusable component with, e.g. parameters and results.</p>
<p>But you are right that it leads to problems when it comes to resource allocation. There are on-going work for executing a whole <em>Pipeline</em> within a single Pod, see <a href="https://github.com/tektoncd/community/blob/main/teps/0044-data-locality-and-pod-overhead-in-pipelines.md" rel="nofollow noreferrer">Tekton Enhancement Proposal 44</a></p>
