From b17d809a4c591a9b17338ad2deab930a6774f1ca Mon Sep 17 00:00:00 2001 From: David Xia Date: Fri, 3 May 2019 20:03:40 -0400 Subject: [PATCH] Clarify which types of lists are replaced (#14149) by kubectl apply. The docs imply that lists whose elements are all primitives are replaced by the applied config instead of being updated. This PR states that explicitly for clarity. --- .../overview/object-management-kubectl/declarative-config.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/overview/object-management-kubectl/declarative-config.md b/content/en/docs/concepts/overview/object-management-kubectl/declarative-config.md index 2887bee6b8..5e827086f9 100644 --- a/content/en/docs/concepts/overview/object-management-kubectl/declarative-config.md +++ b/content/en/docs/concepts/overview/object-management-kubectl/declarative-config.md @@ -585,13 +585,13 @@ Fields that represent maps are merged by comparing each of the subfields or elem Merging changes to a list uses one of three strategies: -* Replace the list. +* Replace the list if all its elements are primitives. * Merge individual elements in a list of complex elements. * Merge a list of primitive elements. The choice of strategy is made on a per-field basis. -#### Replace the list +#### Replace the list if all its elements are primitives Treat the list the same as a primitive field. Replace or delete the entire list. This preserves ordering.