From fa7d7daf7fcbb817248117b2cb2794ead39aa8db Mon Sep 17 00:00:00 2001 From: supereagle Date: Tue, 1 Aug 2017 13:09:36 +0800 Subject: Correct deprecation policy url --- contributors/devel/api_changes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 -- cgit v1.2.3