diff options
| -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`). |