From b0d30f657f25ece6d92f127836cc492c20bc6f1f Mon Sep 17 00:00:00 2001 From: Tim Allclair Date: Fri, 6 Jul 2018 16:48:42 -0700 Subject: [PATCH] Address minor feedback --- keps/sig-node/0014-runtime-class.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/keps/sig-node/0014-runtime-class.md b/keps/sig-node/0014-runtime-class.md index 5f2f087e7..a2b780f52 100644 --- a/keps/sig-node/0014-runtime-class.md +++ b/keps/sig-node/0014-runtime-class.md @@ -106,7 +106,7 @@ iteration: - As a cluster operator, I want to provide multiple runtime options to support a wide variety of workloads. Examples include native linux containers, "sandboxed" containers, and windows containers. -- As a cluster operator, I want to provide stable rolling upgrades or runtimes. For +- As a cluster operator, I want to provide stable rolling upgrades of runtimes. For example, rolling out an update with backwards incompatible changes or previously unsupported features. - As an application developer, I want to select the runtime that best fits my workload. @@ -222,10 +222,6 @@ Examples of runtime parameters include: // way of surfacing behaviors that were previously implicit in docker but not // well defined in Kubernetes. "default-capabilities": "[]" - -// Set the infrastructure container image. More generally, configuring options -// not otherwise exposed in the Kubrenetes API. -"infra-image": "example.com/self-monitoring-pod:v2" ``` _Note: RuntimeClass is intended to be consumed by a single runtime implementation, so parameter keys