KCNA · Question #195
How long should a stable API element in Kubernetes be supported (at minimum) after deprecation?
The correct answer is C. 12 months. A stable API element in Kubernetes must be supported for a minimum of 12 months after it is officially deprecated.
Question
How long should a stable API element in Kubernetes be supported (at minimum) after deprecation?
Options
- A9 months
- B24 months
- C12 months
- D6 months
How the community answered
(27 responses)- B4% (1)
- C93% (25)
- D4% (1)
Why each option
A stable API element in Kubernetes must be supported for a minimum of 12 months after it is officially deprecated.
9 months is not the specified minimum support period for deprecated stable APIs.
24 months is longer than the minimum required support period for deprecated stable APIs.
According to the Kubernetes API deprecation policy, stable API versions must be supported for at least one year (12 months) after their deprecation announcement, allowing users sufficient time to migrate their configurations. This policy ensures backward compatibility and provides a predictable upgrade path for users.
6 months is not the specified minimum support period for deprecated stable APIs; it's too short.
Concept tested: Kubernetes API deprecation policy
Source: https://kubernetes.io/docs/reference/using-api/deprecation-policy/
Topics
Community Discussion
No community discussion yet for this question.