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

wrap by warning shortcodes (#9114)

Browse Source 
* wrap by warning shortcodes

* wrap by warning shortcodes (another)
This commit is contained in:
makocchi
2018-06-18 23:15:31 +09:00
committed by k8s-ci-robot
parent 938116efd7
commit bbdfeaf94f
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/overview/object-management-kubectl/imperative-config.md
+5 -1
View File
@@ -33,6 +33,7 @@ for details.
## How to update objects ## How to update objects
{{< warning >}}
**Warning:** Updating objects with the `replace` command drops all **Warning:** Updating objects with the `replace` command drops all
parts of the spec not specified in the configuration file. This parts of the spec not specified in the configuration file. This
should not be used with objects whose specs are partially managed should not be used with objects whose specs are partially managed
@@ -40,6 +41,7 @@ by the cluster, such as Services of type `LoadBalancer`, where
the `externalIPs` field is managed independently from the configuration the `externalIPs` field is managed independently from the configuration
file. Independently managed fields must be copied to the configuration file. Independently managed fields must be copied to the configuration
file to prevent `replace` from dropping them. file to prevent `replace` from dropping them.
{{< /warning >}}
You can use `kubectl replace -f` to update a live object according to a You can use `kubectl replace -f` to update a live object according to a
configuration file. configuration file.
@@ -110,7 +112,9 @@ several manual steps.
## Defining controller selectors and PodTemplate labels ## Defining controller selectors and PodTemplate labels
**Warning**: Updating selectors on controllers is strongly discouraged. {{< warning >}}
**Warning:** Updating selectors on controllers is strongly discouraged.
{{< /warning >}}
The recommended approach is to define a single, immutable PodTemplate label The recommended approach is to define a single, immutable PodTemplate label
used only by the controller selector with no other semantic meaning. used only by the controller selector with no other semantic meaning.