Show HN: Automated Pipelines to Your Kubernetes Clusters

Re:Show HN: Automated Pipelines to Your Kubernetes Clusters by markbnj on Monday December 12, 2016 @02:44PM (#13161210)

We use CircleCI. The build container is provisioned with docker/gcloud/kubectl. The repo webhook fires on commit, the image is built, a test entrypoint is executed on the image to run tests. If the tests pass the image is pushed to the project repository, and then kubectl is used to update the kubernetes deployments with the new image ref.

[ Parent | on HN ]

Re:Show HN: Automated Pipelines to Your Kubernetes Clusters by gkop on Monday December 12, 2016 @02:53PM (#13161311)

> The build container is provisioned with docker/gcloud/kubectl.

What does this mean? I thought one of the key things that Circle provides is the build container.

[ Parent | on HN ]

Re:Show HN: Automated Pipelines to Your Kubernetes Clusters by markbnj on Monday December 12, 2016 @05:25PM (#13162572)

Yes, circle provides the build container and docker, and our scripts install gcloud and kubectl and authorize a service account that can push to the associated project image repository.

[ Parent | on HN ]

Re:Show HN: Automated Pipelines to Your Kubernetes Clusters by gkop on Monday December 12, 2016 @05:33PM (#13162633)

Gotcha. We're doing the same thing here. The only problem is that Circle doesn't cache the image layers, so we do a full build every time, which takes about 10 minutes.

[ Parent | on HN ]

Re:Show HN: Automated Pipelines to Your Kubernetes Clusters by markbnj on Tuesday December 13, 2016 @01:02PM (#13168913)

Yep same here, that's one of the things we need to improve on to get our deploy times down.

[ Parent | on HN ]