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
Copy file name to clipboardExpand all lines: CHANGELOG.md
+11-1Lines changed: 11 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,21 @@
1
+
## v1.5.0 / 2019-01-10
2
+
3
+
After a testing period of 30 days, there were no additional bugs found or features introduced. Due to no bugs being reported over an in total 41 days period, we feel no more pre-releases are necessary for a stable release.
4
+
5
+
This release's focus was a large architectural change in order to improve performance and resource usage of kube-state-metrics drastically. Special thanks to @mxinden for his hard work on this! See the changelog of the pre-releases for more detailed information and related pull requests.
6
+
7
+
An additional change has been requested to be listed in the release notes:
8
+
9
+
*[CHANGE] Due to removal of the surrounding mechanism the `ksm_resources_per_scrape` and `ksm_scrape_error_total` metrics no longer exists.
10
+
1
11
## v1.5.0-beta.0 / 2018-12-11
2
12
3
13
After a testing period of 11 days, there were no additional bugs found or features introduced.
4
14
5
15
## v1.5.0-alpha.0 / 2018-11-30
6
16
7
17
*[CHANGE] Disable gzip compression of kube-state-metrics responses by default. Can be re-enabled via `--enable-gzip-encoding`. See #563 for more details.
| ksm_scrape_error_total | Counter | Total scrape errors encountered when scraping a resource |`resource`=<resource name>|
110
-
| ksm_resources_per_scrape | Summary | Number of resources returned per scrape |`resource`=<resource name>|
106
+
kube-state-metrics exposes its own general process metrics under `--telemetry-host` and `--telemetry-port` (default 81).
111
107
112
108
### Resource recommendation
113
109
@@ -132,32 +128,32 @@ These numbers are based on [scalability tests](https://github.com/kubernetes/kub
132
128
133
129
Note that if CPU limits are set too low, kube-state-metrics' internal queues will not be able to be worked off quickly enough, resulting in increased memory consumption as the queue length grows. If you experience problems resulting from high memory allocation, try increasing the CPU limits.
134
130
135
-
### kube-state-metrics vs. Heapster(metrics-server)
131
+
### kube-state-metrics vs. metrics-server(Heapster)
136
132
137
-
Heapster([metrics-server](https://github.com/kubernetes-incubator/metrics-server)) is a project which fetches
133
+
[metrics-server](https://github.com/kubernetes-incubator/metrics-server)(Heapster) is a project which fetches
138
134
metrics (such as CPU and memory utilization) from the Kubernetes API server and
139
135
nodes and sends them to various time-series backends such as InfluxDB or Google
140
136
Cloud Monitoring. Its most important function right now is implementing certain
141
137
metric APIs that Kubernetes components like the horizontal pod auto-scaler
142
138
query to make decisions.
143
139
144
-
While Heapster([metrics-server](https://github.com/kubernetes-incubator/metrics-server))'s focus is on forwarding metrics already generated by
140
+
While [metrics-server](https://github.com/kubernetes-incubator/metrics-server)(Heapster)'s focus is on forwarding metrics already generated by
145
141
Kubernetes, kube-state-metrics is focused on generating completely new metrics
146
142
from Kubernetes' object state (e.g. metrics based on deployments, replica sets,
147
-
etc.). The reason not to extend Heapster([metrics-server](https://github.com/kubernetes-incubator/metrics-server)) with kube-state-metrics' abilities is
148
-
because the concerns are fundamentally different: Heapster([metrics-server](https://github.com/kubernetes-incubator/metrics-server)) only needs to fetch,
143
+
etc.). The reason not to extend [metrics-server](https://github.com/kubernetes-incubator/metrics-server)(Heapster) with kube-state-metrics' abilities is
144
+
because the concerns are fundamentally different: [metrics-server](https://github.com/kubernetes-incubator/metrics-server)(Heapster) only needs to fetch,
149
145
format and forward metrics that already exist, in particular from Kubernetes
150
146
components, and write them into sinks, which are the actual monitoring
151
147
systems. kube-state-metrics, in contrast, holds an entire snapshot of
152
148
Kubernetes state in memory and continuously generates new metrics based off of
153
149
it but has no responsibility for exporting its metrics anywhere.
154
150
155
151
In other words, kube-state-metrics itself is designed to be another source for
156
-
Heapster([metrics-server](https://github.com/kubernetes-incubator/metrics-server)) (although this is not currently the case).
152
+
[metrics-server](https://github.com/kubernetes-incubator/metrics-server)(Heapster) (although this is not currently the case).
157
153
158
-
Additionally, some monitoring systems such as Prometheus do not use Heapster([metrics-server](https://github.com/kubernetes-incubator/metrics-server))
154
+
Additionally, some monitoring systems such as Prometheus do not use [metrics-server](https://github.com/kubernetes-incubator/metrics-server)(Heapster)
159
155
for metric collection at all and instead implement their own, but
160
-
[Prometheus can scrape metrics from heapster itself to alert on Heapster(metrics-server)'s health](https://kubernetes.io/docs/tasks/debug-application-cluster/core-metrics-pipeline/).
156
+
[Prometheus can scrape metrics from metrics-server(Heapster) itself to alert on metrics-server(Heapster)'s health](https://kubernetes.io/docs/tasks/debug-application-cluster/core-metrics-pipeline/).
161
157
Having kube-state-metrics as a separate project enables access to these metrics
0 commit comments