A stable API element in Kubernetes should be supported for at least one year after deprecation. This policy ensures that users have sufficient time to migrate to newer versions of the API before the deprecated element is removed in a future release.
this old question no longer valid:
https://kubernetes.io/docs/reference/using-api/deprecation-policy/#:~:text=Rule%20%231%3A%20API,regardless%20of%20track.
Rule #7: Deprecated behaviors must function for no less than 1 year after their announced deprecation.
https://kubernetes.io/docs/reference/using-api/deprecation-policy/#:~:text=Rule%20%237%3A%20Deprecated%20behaviors%20must%20function%20for%20no%20less%20than%201%20year%20after%20their%20announced%20deprecation.
Rule #11b: Metrics, after their announced deprecation, must function for no less than:
STABLE: 3 releases or 9 months (whichever is longer)
BETA: 1 releases or 4 months (whichever is longer)
ALPHA: 0 releases
Refer to : https://kubernetes.io/docs/reference/using-api/deprecation-policy/#:~:text=STABLE%3A%203%20releases%20or%209%20months%20(whichever%20is%20longer)
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
shahy0
1 week, 3 days agopulsefire
6 months agoomerco61
7 months agoCharliesco
7 months, 3 weeks agoeduarte
1 year ago