From 7fef09fee11f869cf0ac0ce82480edb424ed3338 Mon Sep 17 00:00:00 2001 From: Tim Bannister Date: Thu, 6 Jun 2019 06:36:11 +0100 Subject: [PATCH] Explain motivation for RuntimeClass (#14490) --- content/en/docs/concepts/containers/runtime-class.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/content/en/docs/concepts/containers/runtime-class.md b/content/en/docs/concepts/containers/runtime-class.md index d8b025395c..028caaf2f1 100644 --- a/content/en/docs/concepts/containers/runtime-class.md +++ b/content/en/docs/concepts/containers/runtime-class.md @@ -29,6 +29,18 @@ Beta](#upgrading-runtimeclass-from-alpha-to-beta). RuntimeClass is a feature for selecting the container runtime configuration. The container runtime configuration is used to run a Pod's containers. +## Motivation + +You can set a different RuntimeClass between different Pods to provide a balance of +performance versus security. For example, if part of your workload deserves a high +level of information security assurance, you might choose to schedule those Pods so +that they run in a container runtime that uses hardware virtualization. You'd then +benefit from the extra isolation of the alternative runtime, at the expense of some +additional overhead. + +You can also use RuntimeClass to run different Pods with the same container runtime +but with different settings. + ### Set Up Ensure the RuntimeClass feature gate is enabled (it is by default). See [Feature