Skip to content

Latest commit

 

History

History
74 lines (49 loc) · 2.56 KB

kubelet-hypercontainer-runtime.md

File metadata and controls

74 lines (49 loc) · 2.56 KB
Raw

WARNING WARNING WARNING WARNING WARNING

PLEASE NOTE: This document applies to the HEAD of the source tree

If you are using a released version of Kubernetes, you should refer to the docs that go with that version.

Documentation for other releases can be found at releases.k8s.io.

Kubelet HyperContainer Container Runtime

Authors: Pengfei Ni (@feiskyer), Harry Zhang (@resouer)

Abstract

This proposal aims to support HyperContainer 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 implements the CRI interface and exposes a local endpoint to Kubelet. Fakti communicates with hyperd with its gRPC API to manage the lifecycle of sandboxes, containers and images.

frakti

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.

Analytics