How long should a stable API element in Kubernetes be supported (at minimum) after deprecation?
How long should a stable API element in Kubernetes be supported (at minimum) after deprecation?
A stable API element in Kubernetes should be supported for at least 12 months after deprecation. This ensures that users have sufficient time to transition from deprecated API elements to newer versions or alternatives.
C is correct
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)
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.
this old question no longer valid: https://kubernetes.io/docs/reference/using-api/deprecation-policy/#:~:text=Rule%20%231%3A%20API,regardless%20of%20track.