mirror of https://github.com/k3s-io/k3s
46 lines
1.6 KiB
Markdown
46 lines
1.6 KiB
Markdown
|
Kubelet HyperContainer Container Runtime
|
||
|
|
=======================================
|
||
|
|
|
||
|
|
Authors: Pengfei Ni (@feiskyer), Harry Zhang (@resouer)
|
||
|
|
|
||
|
|
## Abstract
|
||
|
|
|
||
|
|
This proposal aims to support [HyperContainer](http://hypercontainer.io) container
|
||
|
|
runtime in Kubelet.
|
||
|
|
|
||
|
|
## Motivation
|
||
|
|
|
||
|
|
HyperContainer is a Hypervisor-agnostic Container Engine that allows you to run Docker images using
|
||
|
|
hypervisors (KVM, Xen, etc.). By running containers within separate VM instances, it offers a
|
||
|
|
hardware-enforced isolation, which is required in multi-tenant environments.
|
||
|
|
|
||
|
|
## Goals
|
||
|
|
|
||
|
|
1. Complete pod/container/image lifecycle management with HyperContainer.
|
||
|
|
2. Setup network by network plugins.
|
||
|
|
3. 100% Pass node e2e tests.
|
||
|
|
4. Easy to deploy for both local dev/test and production clusters.
|
||
|
|
|
||
|
|
## Design
|
||
|
|
|
||
|
|
The HyperContainer runtime will make use of the kubelet Container Runtime Interface. [Fakti](https://github.com/kubernetes/frakti) implements the CRI interface and exposes
|
||
|
|
a local endpoint to Kubelet. Fakti communicates with [hyperd](https://github.com/hyperhq/hyperd)
|
||
|
|
with its gRPC API to manage the lifecycle of sandboxes, containers and images.
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
## Limitations
|
||
|
|
|
||
|
|
Since pods are running directly inside hypervisor, host network is not supported in HyperContainer
|
||
|
|
runtime.
|
||
|
|
|
||
|
|
## Development
|
||
|
|
|
||
|
|
The HyperContainer runtime is maintained by <https://github.com/kubernetes/frakti>.
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
|
||
|
|
[]()
|
||
|
|
<!-- END MUNGE: GENERATED_ANALYTICS -->
|