Go to file
Archana Shinde 8342ca1d04 kata-deploy: Add runtime config for crio if it does not exist
Rather than add the config for kata-qemu and kata-fc unconditionally,
the script now checks if the runtime config exists.
If it exists, then do not chnage the path for the runtime.
The user may have configured this to a specific path for testing
local chnages.

Fixes #374

Signed-off-by: Archana Shinde <archana.m.shinde@intel.com>
2019-03-13 16:13:00 -07:00
.ci kernel: remove build-kernel_test.sh 2019-03-06 08:51:17 -06:00
ccloudvm ccloudvm: update kata install URL 2019-02-04 17:25:05 +01:00
kata-deploy kata-deploy: Add runtime config for crio if it does not exist 2019-03-13 16:13:00 -07:00
kernel Merge pull request #381 from chavafg/topic/rm-kernel-test-script 2019-03-06 10:45:40 -06:00
obs-packaging pkgs: runtime: spec fix qemu path 2019-01-30 08:49:34 -06:00
release Merge pull request #209 from jcvenegas/release-process-md 2019-02-14 09:28:41 -06:00
scripts s390x: add support to build qemu 2019-02-07 16:49:57 +01:00
snap snap: release 1.5.1 2019-03-05 11:12:17 -06:00
static-build Firecracker: Add support for firecracker packaging 2019-01-17 09:37:31 -08:00
.gitignore snap: remove snap-build scripts 2019-02-21 10:51:50 -06:00
CODE_OF_CONDUCT.md docs: Add CoC and contributing doc 2018-02-05 15:33:30 +00:00
CONTRIBUTING.md docs: Add CoC and contributing doc 2018-02-05 15:33:30 +00:00
LICENSE Initial commit 2018-02-02 09:27:48 +00:00
Makefile kernel: remove build-kernel_test.sh 2019-03-06 08:51:17 -06:00
README.md kata-deploy: add support for deploying Kata on K8S 2018-07-10 18:52:05 +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.