This enables KubernetesBuildExecutor to be subclassed and used with other builders such as Kaniko which doesn't need an mounted host socket.
With this BinderHub change it should be possible to use Kaniko using just the traitlets config using something like the following, instead of overriding the KubernetesBuildExecutor as suggested in https://github.com/jupyterhub/repo2docker/issues/560:
This enables KubernetesBuildExecutor to be subclassed and used with other builders such as Kaniko which doesn't need an mounted host socket.
With this BinderHub change it should be possible to use Kaniko using just the traitlets config using something like the following, instead of overriding the
KubernetesBuildExecutor
as suggested in https://github.com/jupyterhub/repo2docker/issues/560:I've made the volumes into an overridable method so that additional volumes could be added by subclasses.
Related: