kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #42217 from logicalhan/instrumentation-docs 

amend deprecation policy on stability framework
dev-1.28
Kubernetes Prow Robot 2023-08-28 03:49:44 -07:00 committed by GitHub
parent e05d2b72db f2f5a7e284
commit 53777ca986
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
content/en/docs/reference/using-api/deprecation-policy.md
View File

@ -441,6 +441,12 @@ deprecating and removing a metric are as follows:
* **STABLE: 3 releases or 9 months (whichever is longer)** * **STABLE: 3 releases or 9 months (whichever is longer)**
* **BETA: 1 releases or 4 months (whichever is longer)** * **BETA: 1 releases or 4 months (whichever is longer)**
* **ALPHA: 0 releases** * **ALPHA: 0 releases**
It is permissible, in certain cases, for metrics to skip stability levels in the process
of graduation. This is done on a case by case basis, at the discretion of the SIG which
owns the metric. Since the stability framework was introduced far after the conception
of Kubernetes, there are many existing metrics which may not want or need to go through
the entire graduation process, since people already likely rely on these metrics.
Deprecated metrics will have their description text prefixed with a deprecation notice Deprecated metrics will have their description text prefixed with a deprecation notice
string '(Deprecated from x.y)' and a warning log will be emitted during metric string '(Deprecated from x.y)' and a warning log will be emitted during metric