@kneal and I are going to begin by writing the ability to create volumes in Kubernetes.

It appears the gitRepo volume type is deprecated:

Warning: The gitRepo volume type is deprecated. To provision a container with a git repo, mount an EmptyDir into an InitContainer that clones the repo using git, then mount the EmptyDir into the Pod’s container.

We will follow the recommended guidelines to use emptyDir instead 👍

After some trial and error, we've come to a roadblock 😞

Unfortunately, it would appear that Kubernetes prevents the ability to patch specific fields in a Pod. Specifically, it appears that we're unable to patch some Container fields which is required to maintain a "1 pod per build" strategy.

The initial plan was to create a single pod per build, and then to patch that pod with each container (step) from the pipeline.

The error message we receive:

spec: Forbidden: pod updates may not change fields other than `spec.containers[*].image`, `spec.initContainers[*].image`, `spec.activeDeadlineSeconds` or `spec.tolerations` (only additions to existing tolerations)

Issue with more information:

kubernetes/kubernetes#9043

Create separate runtime package:

go-vela/pkg-runtime#1

Store Kubernetes pod in client struct:

go-vela/pkg-runtime#2

Use the go-vela/compiler for our runtime CLI:

go-vela/pkg-runtime#3

Create a working runtime CLI:

go-vela/pkg-runtime#4

Add container wait logic for Kubernetes:

go-vela/pkg-runtime#5

Add container tail logic for Kubernetes:

go-vela/pkg-runtime#6

Use default (strategic merge) patch for Kubernetes pods:

go-vela/pkg-runtime#7

Add logic to remove Kubernetes resources:

go-vela/pkg-runtime#8

Tune Kubernetes tail backoff for large pipelines
go-vela/pkg-runtime#9

Implement the inspect process for Kubernetes
go-vela/pkg-runtime#10

Make the namespace configurable
go-vela/pkg-runtime#11

Add function to create new runtime:

go-vela/pkg-runtime#12

Add validate logic for runtime:

go-vela/pkg-runtime#13

Add actions pipeline:

go-vela/pkg-runtime#14