#codefresh (2021-05)


Archive: https://archive.sweetops.com/codefresh/


btai avatar

do end users of codefresh need to do anything about the kubernetes dockershim deprecation in late 2021? I know that it’ll break the popular docker in docker pattern that is used by alot of CI providers, so I’m wondering if that’s something we need to worry about on our end. https://kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-and-docker/

Don't Panic: Kubernetes and Docker

Authors: Jorge Castro, Duffie Cooley, Kat Cosgrove, Justin Garrison, Noah Kantrowitz, Bob Killen, Rey Lejano, Dan “POP” Papandrea, Jeffrey Sica, Davanum “Dims” Srinivas Kubernetes is deprecating Docker as a container runtime after v1.20. You do not need to panic. It’s not as dramatic as it sounds. TL;DR Docker as an underlying runtime is being deprecated in favor of runtimes that use the Container Runtime Interface (CRI) created for Kubernetes. Docker-produced images will continue to work in your cluster with all runtimes, as they always have.

dustinvb avatar

The main concern on our side before with this deprecation was our agents running on customer clusters. We’ve tested our agent and confirmed it runs issue free on Kubernetes without dockershim.

See item 3: https://codefresh.io/docs/docs/administration/codefresh-runner/#prerequisites

Codefresh Runner

Run Codefresh pipelines on your private Kubernetes cluster

btai avatar

cool beans

btai avatar

(i don’t use self hosted runners but sounds like no work on our side for saas either)

Oliver avatar

Hey guys, question, once you got your tests and deployments automated, what was your strategy for one-off tasks? I mean for those cases where you need to run a command or an app method to quickly fix an issue

dustinvb avatar

Oliver, can you expand some on this? Normally you won’t see automation in place for these ad-hoc fixes or changes only something that you would do more than once.