3 ms·
Does Kubernetes support adding "middleware" between it and docker? ie when it comes time to do a container start, it calls my custom plugin instead of docker di
by djb_hackernews 9y ago
Does Kubernetes support adding "middleware" between it and docker? ie when it comes time to do a container start, it calls my custom plugin instead of docker directly? I read the docs about extensibility and it didn't seem so.
- gtirloni 9y agoYou're probably interested in the Container Runtime Interface [0] 0 - http://blog.kubernetes.io/2016/12/container-runtime-interface-cri-in-kubernetes.html http://blog.kubernetes.io/2016/12/container-runtime-interfac...
- puzzle 9y agoWhat kind of plugins are you thinking of?
- djb_hackernews 9y agoThis is a very simple example. But we require setting the pid limit cgroup. Right now Kubernetes doesn't support this (again, just an example, there are a lot of things kubernetes doesn't support that we need beyond pid limits). So it'd be nice to be able to proxy the call to docker to inject our own config before hitting docker. It looks like CRI is exactly what we'd need, possibly maintaining our own fork of the docker shim? Trying to figure out if there is a way to put in arbitrary data in the config sent to the docker shim[0] [0] https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/apis/cri/v1alpha1/runtime/api.pb.go https://github.com/kubernetes/kubernetes/blob/master/pkg/kub...
- davidopp_ 9y agoThat idea was proposed here: https://github.com/kubernetes/features/issues/246 https://github.com/kubernetes/features/issues/246 ; there's a pretty thorough design doc linked to from the issue. The decision was made not to add it to the system for now (see the issue for discussion).