From bbdfeaf94f47430bd951257b93c1e6520d31ff61 Mon Sep 17 00:00:00 2001 From: makocchi Date: Mon, 18 Jun 2018 23:15:31 +0900 Subject: [PATCH] wrap by warning shortcodes (#9114) * wrap by warning shortcodes * wrap by warning shortcodes (another) --- .../overview/object-management-kubectl/imperative-config.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/content/en/docs/concepts/overview/object-management-kubectl/imperative-config.md b/content/en/docs/concepts/overview/object-management-kubectl/imperative-config.md index a76a0667ad..7a44a27fc5 100644 --- a/content/en/docs/concepts/overview/object-management-kubectl/imperative-config.md +++ b/content/en/docs/concepts/overview/object-management-kubectl/imperative-config.md @@ -33,6 +33,7 @@ for details. ## How to update objects +{{< warning >}} **Warning:** Updating objects with the `replace` command drops all parts of the spec not specified in the configuration file. This 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 file. Independently managed fields must be copied to the configuration file to prevent `replace` from dropping them. +{{< /warning >}} You can use `kubectl replace -f` to update a live object according to a configuration file. @@ -110,7 +112,9 @@ several manual steps. ## 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 used only by the controller selector with no other semantic meaning.