From 4704761e606c5932b7826ed0b414fb717f9d2608 Mon Sep 17 00:00:00 2001 From: johndmulhausen Date: Thu, 25 Feb 2016 14:40:54 -0800 Subject: [PATCH] Update configuring-containers.md --- _includes/masterdocs/docs/user-guide/configuring-containers.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/_includes/masterdocs/docs/user-guide/configuring-containers.md b/_includes/masterdocs/docs/user-guide/configuring-containers.md index 04c390aedc1..e36f1ec5a7d 100644 --- a/_includes/masterdocs/docs/user-guide/configuring-containers.md +++ b/_includes/masterdocs/docs/user-guide/configuring-containers.md @@ -57,8 +57,7 @@ Let's say you specified `entrypoint` instead of `command`. You'd see output as f ```shell I0709 06:33:05.600829 14160 schema.go:126] unknown field: entrypoint -I0709 06:33:05.600988 14160 schema.go:129] this may be a false alarm, see http://issue.k8s.io/6842 -pods/hello-world +I0709 06:33:05.600988 14160 schema.go:129] this may be a false alarm, see http://issue.k8s.io/6842 pods/hello-world ``` `kubectl create --validate` currently warns about problems it detects, but creates the resource anyway, unless a required field is absent or a field value is invalid. Unknown API fields are ignored, so be careful. This pod was created, but with no `command`, which is an optional field, since the image may specify an `Entrypoint`.