rm --record from kubectl conventions
This commit is contained in:
parent
f7bd5fab1a
commit
2d3d7b9162
|
@ -27,7 +27,6 @@ For a stable output in a script:
|
|||
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)).
|
||||
* 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.
|
||||
* Switch to configuration files checked into source control for features that are needed, but not expressible via `kubectl run` flags.
|
||||
|
||||
|
|
Loading…
Reference in New Issue