diff options
| author | supereagle <jmyue@hotmail.com> | 2017-02-24 14:33:58 +0800 |
|---|---|---|
| committer | supereagle <jmyue@hotmail.com> | 2017-02-24 14:33:58 +0800 |
| commit | 264bd0f4a6667342a8d846f3eee473fc9ce5e390 (patch) | |
| tree | 2050998c74ebf6382d2d2baad469ee6160e63ee4 | |
| parent | 2d53ed8ddb6045fa64eb17091278421c3413bee9 (diff) | |
fix url error
| -rwxr-xr-x | contributors/devel/api_changes.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/devel/api_changes.md b/contributors/devel/api_changes.md index b566e39f..4d181a2a 100755 --- a/contributors/devel/api_changes.md +++ b/contributors/devel/api_changes.md @@ -215,7 +215,7 @@ runs just prior to conversion. That works fine when the user creates a resource from a hand-written configuration -- clients can write either field and read either field, but what about creation or update from the output of GET, or update via PATCH (see -[In-place updates](https://kubernetes.io/docs/user-guide/managing-deployments.md#in-place-updates-of-resources))? +[In-place updates](https://kubernetes.io/docs/user-guide/managing-deployments/#in-place-updates-of-resources))? In this case, the two fields will conflict, because only one field would be updated in the case of an old client that was only aware of the old field (e.g., `height`). |