diff options
| author | supereagle <jmyue@hotmail.com> | 2017-08-01 13:09:36 +0800 |
|---|---|---|
| committer | supereagle <jmyue@hotmail.com> | 2017-08-01 13:09:36 +0800 |
| commit | fa7d7daf7fcbb817248117b2cb2794ead39aa8db (patch) | |
| tree | 022dfc23462b51584370d2e54cbbd9a0d1225564 | |
| parent | 7eb5cac28a91b9e383d807d9750f1a27b69f85d9 (diff) | |
Correct deprecation policy url
| -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 3d9f1e18..dc06aeb5 100755 --- a/contributors/devel/api_changes.md +++ b/contributors/devel/api_changes.md @@ -285,7 +285,7 @@ was added. * For [Unions](api-conventions.md#unions), sets of fields where at most one should be set, it is acceptable to add a new option to the union if the [appropriate conventions](api-conventions.md#objects) were followed in the original object. - Removing an option requires following the [deprecation process](https://kubernetes.io/docs/deprecation-policy/). + Removing an option requires following the [deprecation process](https://kubernetes.io/docs/reference/deprecation-policy/). * Changing any validation rules always has the potential of breaking some client, since it changes the assumptions about part of the API, similar to adding new enum values. Validation rules on spec fields can |