From 40e57e4c84e1adb4206f3dc77403311af52b6811 Mon Sep 17 00:00:00 2001 From: Jordan Liggitt Date: Wed, 30 May 2018 21:11:55 -0400 Subject: [PATCH] clarify version removal restriction (#8825) --- content/en/docs/reference/using-api/deprecation-policy.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/content/en/docs/reference/using-api/deprecation-policy.md b/content/en/docs/reference/using-api/deprecation-policy.md index 1a78c186ce..32bb782e1e 100644 --- a/content/en/docs/reference/using-api/deprecation-policy.md +++ b/content/en/docs/reference/using-api/deprecation-policy.md @@ -84,7 +84,10 @@ no less than:** This covers the maximum supported version skew of 2 releases. NOTE: Until [#52185](https://github.com/kubernetes/kubernetes/issues/52185) is -resolved, no API versions may be removed. +resolved, no API versions that have been persisted to storage may be removed. +Serving REST endpoints for those versions may be disabled (subject to the +deprecation timelines in this document), but the API server must remain capable +of decoding/converting previously persisted data from storage. **Rule #4b: The "preferred" API version and the "storage version" for a given group may not advance until after a release has been made that supports both the