> Lot's of tools to solve problems that K8s already solves In fairness, Concourse predates Kubernetes and was invented developed to support a team working on a

> Lot's of tools to solve problems that K8s already solves In fairness, Concourse predates Kubernetes and was invented developed to support a team working on a different container scheduler (Diego, similar vintage to Kubernetes). Otherwise you're right. The pain of carrying around its own container scheduling, worker management etc has been a notably hefty thorn in the side of Concourse for the last two years or so. It should go away as Concourse gets rebased onto Kubernetes. > The Syntax, is K8S YAML syntax, the same with a couple more things, very little learning curve if you know K8S YAMLs, Concourse is a very different thing. As part of my work in and around Knative Build, Topher Bullock and I wrote a little façade Kubernetes controller[0] that lets you send pipelines and see builds from kubectl. Basically it looks like an existing Concourse pipeline, but with the usual k8s boilerplate. I'm not sure what the final Concourse-on-Kubernetes will look like. kubectl is showing one-size-fits-all discomfort (see, for example, knctl[1]) and I am not sold that CRDs are suitable for every purpose. 2018 is clearly The Year of the CRD, so I figure we're about 18 months away from the trough of disillusionment on those. [0] https://github.com/jchesterpivotal/knative-build-pipeline-poc/commits/master https://github.com/jchesterpivotal/knative-build-pipeline-po... [1] https://github.com/cppforlife/knctl https://github.com/cppforlife/knctl