Kubernetes Metrics Server: Difference between revisions
(→TODO) |
|||
| Line 11: | Line 11: | ||
The Kubernetes metrics server, also referred to as "metrics-server" is a lightweight, short-term, in-memory server to collect and expose [[Metrics_in_Kubernetes#Resource_Metrics|resource metrics]]. metrics-server is used as part of the Kubernetes [[Metrics_in_Kubernetes#Resource_Metrics_Pipeline|resource metrics pipeline]]. The metrics server discovers all nodes on the cluster and queries each node's [[kubelet#Metrics_Collection|kubelet]] for [[Metrics_in_Kubernetes#Resource_Metrics|resource metrics]] (CPU and memory) then exposes these metric via the [[Metrics_in_Kubernetes#Resource_Metrics_API|Resource Metrics API]]. The Resource Metrics API is not available if the metrics server is not deployed. The API is served at /metrics/resource/v1beta1 on the kubelet's authenticated and read-only ports. The metrics server is registered with the main API through [[Kubernetes Aggregation Layer|Kubernetes aggregator]]. | The Kubernetes metrics server, also referred to as "metrics-server" is a lightweight, short-term, in-memory server to collect and expose [[Metrics_in_Kubernetes#Resource_Metrics|resource metrics]]. metrics-server is used as part of the Kubernetes [[Metrics_in_Kubernetes#Resource_Metrics_Pipeline|resource metrics pipeline]]. The metrics server discovers all nodes on the cluster and queries each node's [[kubelet#Metrics_Collection|kubelet]] for [[Metrics_in_Kubernetes#Resource_Metrics|resource metrics]] (CPU and memory) then exposes these metric via the [[Metrics_in_Kubernetes#Resource_Metrics_API|Resource Metrics API]]. The Resource Metrics API is not available if the metrics server is not deployed. The API is served at /metrics/resource/v1beta1 on the kubelet's authenticated and read-only ports. The metrics server is registered with the main API through [[Kubernetes Aggregation Layer|Kubernetes aggregator]]. | ||
The metrics server is not meant for non-autoscaling purposes. It should not be used to forward metrics to monitoring solutions, or as a source of monitoring solution metrics. | |||
=Operations= | =Operations= | ||
{{Internal|Kubernetes Metrics Server Operations|Metrics Server Operations}} | {{Internal|Kubernetes Metrics Server Operations|Metrics Server Operations}} | ||
Revision as of 01:07, 6 October 2020
External
- https://github.com/kubernetes-incubator/metrics-server
- https://github.com/kubernetes/community/blob/master/contributors/design-proposals/instrumentation/metrics-server.md
Internal
Overview
The Kubernetes metrics server, also referred to as "metrics-server" is a lightweight, short-term, in-memory server to collect and expose resource metrics. metrics-server is used as part of the Kubernetes resource metrics pipeline. The metrics server discovers all nodes on the cluster and queries each node's kubelet for resource metrics (CPU and memory) then exposes these metric via the Resource Metrics API. The Resource Metrics API is not available if the metrics server is not deployed. The API is served at /metrics/resource/v1beta1 on the kubelet's authenticated and read-only ports. The metrics server is registered with the main API through Kubernetes aggregator.
The metrics server is not meant for non-autoscaling purposes. It should not be used to forward metrics to monitoring solutions, or as a source of monitoring solution metrics.