Eric Ernst 5db1ba5710 kata-deploy: add support for runtime class, firecracker
Simplify the yaml and combine the prior scripts. The resulting script,
kata-deploy.sh, is used for  install and configuration and
removal for CRI-O and containerd. While this could be used standalone
outside of daemonsets, today it will sleep infinity after processing the
request, since it is assumed to be called by a daemon.

By checking the CRI runtime within the script itself, we no longer need
to support many daemonsets for deploy - just a single. Still requires a
seperate cleanup daemonset (for restarting the CRI runtime), and an
RBAC.

Verified with CRI-O -- containerd testing WIP

Throwing this up now for feedback since I do not bash good.

Signed-off-by: Eric Ernst <eric.ernst@intel.com>
Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
2019-01-31 21:12:40 -08:00
2018-05-23 11:02:43 -05:00
2019-01-18 02:55:44 -05:00
2019-01-31 21:12:40 -08:00
2018-02-05 15:33:31 +00:00
2018-02-02 09:27:48 +00:00

Kata Containers packaging

Kata Containers currently supports packages for many distributions. Tooling to aid in creating these packages are contained within this repository.

In addition, Kata build artifacts are available within a container image, created by a Dockerfile. Reference daemonsets are provided in kata-deploy, which make installation of Kata Containers in a running Kubernetes Cluster very straightforward.

Languages
Rust 58%
Go 24.6%
Shell 10.1%
RPC 5.3%
Makefile 1%
Other 0.9%