vbatts/cncf-toc
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

proposals: add pod definition link

Browse source
This commit is contained in:
Jonathan Boulle 2017-03-21 16:59:59 +01:00
parent d6ec4ece81
commit 7f5f40fb25
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
proposals/rkt.adoc
View file

@ -6,7 +6,7 @@
rkt is an application container engine developed for modern production cloud-native environments. It features a pod-native approach, a pluggable execution architecture, and a well-defined surface area that makes it ideal for integration with other systems. rkt is an application container engine developed for modern production cloud-native environments. It features a pod-native approach, a pluggable execution architecture, and a well-defined surface area that makes it ideal for integration with other systems.
The core execution unit of rkt is the _pod_, a collection of one or more applications executing in a shared context. (rkt's pods are synoymous with the concept in the Kubernetes orchestration system). rkt allows users to apply different configurations (like isolation parameters) at both pod-level and at the more granular per-application level. rkt's architecture means that each pod executes directly in the classic Unix process model (i.e. there is no central daemon), in a self-contained, isolated environment. The core execution unit of rkt is the _pod_, a collection of one or more applications executing in a shared context. (rkt's pods are synoymous with [the concept in the Kubernetes orchestration system](https://kubernetes.io/docs/user-guide/pods/#what-is-a-pod)). rkt allows users to apply different configurations (like isolation parameters) at both pod-level and at the more granular per-application level. rkt's architecture means that each pod executes directly in the classic Unix process model (i.e. there is no central daemon), in a self-contained, isolated environment.
rkt's daemonless model makes it highly suitable for integration with process managers like systemd, or for embedding in agents like the kubelet or Mesos agent. Its "staged" architecture - separating the user interface from its containerisation phase - allows it to support different isolation technologies: the mainstream rkt project includes implementations like QEMU and LKVM, as well as the default "classic" Linux containers implementation of cgroups and namespaces. Furthermore, while rkt development is currently targeted primarily at GNU/Linux distributions, the staged architecture makes it possible to extend support to other platforms without fundamentally changing rkt's external interfaces. rkt's daemonless model makes it highly suitable for integration with process managers like systemd, or for embedding in agents like the kubelet or Mesos agent. Its "staged" architecture - separating the user interface from its containerisation phase - allows it to support different isolation technologies: the mainstream rkt project includes implementations like QEMU and LKVM, as well as the default "classic" Linux containers implementation of cgroups and namespaces. Furthermore, while rkt development is currently targeted primarily at GNU/Linux distributions, the staged architecture makes it possible to extend support to other platforms without fundamentally changing rkt's external interfaces.