From c6f84966c677381085b792a128cde9fb514464b6 Mon Sep 17 00:00:00 2001 From: Christian Jantz Date: Thu, 28 Mar 2019 11:53:22 +0100 Subject: [PATCH] Fixed a typo in field merge semantics --- docs/book/pages/app_management/field_merge_semantics.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/book/pages/app_management/field_merge_semantics.md b/docs/book/pages/app_management/field_merge_semantics.md index 50e9cf61..d9b43f36 100644 --- a/docs/book/pages/app_management/field_merge_semantics.md +++ b/docs/book/pages/app_management/field_merge_semantics.md @@ -45,7 +45,7 @@ to a default value by the apiserver, or continuously adjusted by a Controller su and HorizontalPodAutoscaler. {% method %} -### Last Applied Resource Condfig +### Last Applied Resource Config When Apply creates or updates a Resource, it writes the Resource Config it Applied to an annotation on the Resource. This allows it to compare the last Resource Config it Applied to the current Resource @@ -474,4 +474,4 @@ To ignore values set by `kubectl edit` or `kubectl set`: - Remove the field from the Resource Config This is the same technique for retaining values set by cluster components such as autoscalers. -{% endpanel %} \ No newline at end of file +{% endpanel %}