Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
How does the current Concourse runtime (garden + baggageclaim) map to Kubernetes runtime as a whole (not related to Tekton)
Another thing regarding volume management, we would need to know when a a task has completed and the output is ready to be moved (via whatever volume-management logic we end up using).
While Tekton allows us to run containers sequentially, k8s doesn't offer much natively (outside of putting everything as an initContainer). And since pods are deleted as soon as their workloads are complete, we would need some way to figure out that the work container is done and and do stuff from within the pod.
There is an upcoming enhancement (kubernetes/enhancements#753) which would allow us to run a container that only gets terminated after the work containers has exited.
In general (K8s or tekton) I’d suggest looking at CSI 1.x which allows you to easily build a pluggable storage engine for PVCs.
This way you’re not at the mercy of arbitrary volume attach/detach at the IaaS which is very slow, you can build on some kind of shared COW fs with snapshots eg. Portworx, Ceph, or even a simple per-host Overlay etc.