From bf5fee07c5e0a774e95e9326206907ecc294d3a1 Mon Sep 17 00:00:00 2001 From: chentao1596 Date: Thu, 11 Jan 2018 10:45:47 +0800 Subject: [PATCH] Update conventions.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit There should be a space between `--record` and "to"。 --- docs/reference/kubectl/conventions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/kubectl/conventions.md b/docs/reference/kubectl/conventions.md index faed88a078..91856a73cb 100644 --- a/docs/reference/kubectl/conventions.md +++ b/docs/reference/kubectl/conventions.md @@ -24,7 +24,7 @@ If you need stable output in a script, you should: In order for `kubectl run` to satisfy infrastructure as code: * Always tag your image with a version-specific tag and don't move that tag to a new version. For example, use `:v1234`, `v1.2.3`, `r03062016-1-4`, rather than `:latest` (see [Best Practices for Configuration](/docs/concepts/configuration/overview/#container-images) for more information). -* If the image is lightly parameterized, capture the parameters in a checked-in script, or at least use `--record`to annotate the created objects with the command line. +* If the image is lightly parameterized, capture the parameters in a checked-in script, or at least use `--record` to annotate the created objects with the command line. * If the image is heavily parameterized, definitely check in the script. * If features are needed that are not expressible via `kubectl run` flags, switch to configuration files checked into source control. * Pin to a specific [generator](#generators) version, such as `kubectl run --generator=deployment/v1beta1`.