patternkubernetesMinor
Why Run Concourse CI in Kubernetes
Viewed 0 times
concoursekuberneteswhyrun
Problem
I've just started exploring Kubernetes and Concourse CI. Learning still, so I'm still understanding all the concepts. Forgive me if this question sounds naive.
Why would we deploy Concourse CI in Kubernetes. Is it just for the ease of deployment? I mean concourse has its own way for scaling workers which itself if I've understood is through containers.
So why run something that can already scale and handle containers(I mean concourse) inside Kubernetes?
Why would we deploy Concourse CI in Kubernetes. Is it just for the ease of deployment? I mean concourse has its own way for scaling workers which itself if I've understood is through containers.
So why run something that can already scale and handle containers(I mean concourse) inside Kubernetes?
Solution
In our case yes, it is just ease of deployment/operations. We have existing skills with k8s and that's what we're most comfortable operating.
I guess you're right that its somewhat odd to run Concourse's scheduling inside of k8s scheduling, and it would be great to see Concourse being able to leverage Kubernetes directly at some point.
I guess you're right that its somewhat odd to run Concourse's scheduling inside of k8s scheduling, and it would be great to see Concourse being able to leverage Kubernetes directly at some point.
Context
StackExchange DevOps Q#3362, answer score: 2
Revisions (0)
No revisions yet.