Hi!
I’m currently playing around with KubeSolo in an embedded/Yocto environment and opened this as some kind of RFC to check whether this direction makes sense upstream.
In Yocto systems, runtime components are often provided as independent OS packages/services:
- containerd / cri-o
- oci runtime (crun, runc)
- oci images
- cni plugins/config
In such setups, KubeSolo should be able to consume host-provided dependencies without embedding/extracting runtime artifacts.
To make that work, I would like to propose some kind of external_deps build-flag, to avoid the embedding of runtime artifacts and instead use the system-provided dependencies.
What do you think about having such a feature upstream?
Hi!
I’m currently playing around with KubeSolo in an embedded/Yocto environment and opened this as some kind of RFC to check whether this direction makes sense upstream.
In Yocto systems, runtime components are often provided as independent OS packages/services:
In such setups, KubeSolo should be able to consume host-provided dependencies without embedding/extracting runtime artifacts.
To make that work, I would like to propose some kind of
external_depsbuild-flag, to avoid the embedding of runtime artifacts and instead use the system-provided dependencies.What do you think about having such a feature upstream?