You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[Not attached to a release milestone](#not-attached-to-a-release-milestone)
52
56
<!-- /toc -->
53
57
54
58
## Summary
@@ -91,7 +95,7 @@ As Kubernetes currently rewrites meta labels of containers to “well-known” `
91
95
92
96
API server histogram latency buckets run from 125ms to 8s. This range does not accurately model most API server request latencies, which could run as low as 1ms for GETs or as high as 60s before hitting the API server global timeout.
Make prober metrics introduced in https://github.com/kubernetes/kubernetes/pull/61369 conform to the [Kubernetes instrumentation guidelines](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/instrumentation.md).
@@ -169,6 +167,10 @@ Risks include users upgrading Kubernetes, but not updating their usage of Kubern
169
167
170
168
To prevent this, we will implement recording rules for Prometheus that allow best effort backward compatibility as well as update uses of breaking metric usages in the [Kubernetes monitoring mixin](https://github.com/kubernetes-monitoring/kubernetes-mixin), a widely used collection of Prometheus alerts and Grafana dashboards for Kubernetes.
171
169
170
+
## Test Plan
171
+
172
+
Each individual change for this KEP must be accompanied with appropriate unit tests. As the scope of changes are provided are on the level of individual metrics, integration testing is not required.
173
+
172
174
## Deprecation Plan
173
175
174
176
In our efforts to change existing old metrics, we flag them `(Deprecated)` in the front of metrics help text.
@@ -177,10 +179,63 @@ These old metrics will be deprecated in v1.14 and coexist with the new replaceme
177
179
178
180
The release target of removing the deprecated metrics is v1.15.
179
181
182
+
Prior to removing deprecated metrics, we will attend appropriate community meetings (i.e. SIG Node) to provide sufficient notice.
183
+
180
184
## Graduation Criteria
181
185
182
186
All metrics exposed by components from kubernetes/kubernetes follow Prometheus best practices and (nice to have) tooling is built and enabled in CI to prevent simple violations of said best practices.
183
187
184
188
## Implementation History
185
189
186
-
Multiple pull requests have already been opened, but not merged as of writing of this document.
190
+
As of release 1.17, this KEP is considered fully implemented.
191
+
192
+
### 1.14
193
+
194
+
- Use prometheus conventions for workqueue metrics [#71300](https://github.com/kubernetes/kubernetes/pull/71300)
0 commit comments