kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update add-new-patchStrategy-to-clear-fields-not-present-in-patch.md

This commit is contained in:
Phinoceslee 2017-11-14 14:51:12 +08:00 committed by GitHub
parent 9d535acf15
commit f966ecd94c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
contributors/design-proposals/api-machinery/add-new-patchStrategy-to-clear-fields-not-present-in-patch.md
View File

@ -299,7 +299,7 @@ Each field present in the request will be merged with the live config.
There are 2 reasons of avoiding this logic:
- Using `$patch` as directive key will break backward compatibility.
But can easily fixed by using a different key, e.g. `retainKeys: true`.
But can easily be fixed by using a different key, e.g. `retainKeys: true`.
Reason is that `$patch` has been used in earlier releases.
If we add new value to this directive,
the old server will reject the new patch due to not knowing the new value.