whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

rm --record from kubectl conventions

Browse Source
This commit is contained in:
Marcin Niemira
2020-04-06 00:02:34 +10:00
committed by bryan
parent 28d629b47d
commit 4ee155e78b
1 changed files with 0 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/reference/kubectl/conventions.md
-1
View File
@@ -27,7 +27,6 @@ For a stable output in a script:
For `kubectl run` to satisfy infrastructure as code: For `kubectl run` to satisfy infrastructure as code:
* Tag the 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` (For more information, see [Best Practices for Configuration](/docs/concepts/configuration/overview/#container-images)). * Tag the 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` (For more information, see [Best Practices for Configuration](/docs/concepts/configuration/overview/#container-images)).
* Capture the parameters in a checked-in script, or at least use `--record` to annotate the created objects with the command line for an image that is lightly parameterized.
* Check in the script for an image that is heavily parameterized. * Check in the script for an image that is heavily parameterized.
* Switch to configuration files checked into source control for features that are needed, but not expressible via `kubectl run` flags. * Switch to configuration files checked into source control for features that are needed, but not expressible via `kubectl run` flags.