v0.3.6

Installation

kubectl apply -f https://github.com/kubernetes-sigs/metrics-server/releases/download/v0.3.6/components.yaml

Changes since v0.3.5

• 🐛 Don't break metric storage when duplicate pod metrics encountered

v0.3.5

Changes since v0.3.4:

• Use protobuf instead of json for communication with apiserver
• Upgrade the apiVersion to apps/v1 for deploymen

v0.3.4

Changes since v0.3.3:

• Match field selectors in List Pod Metrics and List Node Metrics APIs
• Pass only_cpu_and_memory parameter to Summary API call

v0.3.3

Changes since v0.3.2

• Bump Kubernetes version to 1.14
• Build the image on distroless

v0.3.2

Changes since v0.3.1

• Add kubelet-certificate-authority flag
• 🐛 Ignore pod not in Running phase
• 🐛 Do not skip unready nodes
• Scrape metrics on startup

v0.3.1

Changes since v0.3.0

• 🐛 ensure that missing pod/node data doesn't invalidate an entire node's results

v0.3.0

⚠️ This release has significant changes, including new flag names. You may need to update your deployment configurations if you've set any flags. See the README for more information ⚠️

Changes since v0.3.0-alpha.1

• 🎉 update to latest kubernetes dependencies, allowing automatic use of delegated auth on clusters without client certificate auth enabled

• 🐛 ensure earliest timestamps are always reported for metric points. This means it's safe to assume that if a metric point came after pod initialization (factoring in the window), all metrics contained therein came from after pod initialization.

• ⚠️ / 🎉 change reported window size to 30s, to be more accurate (cAdvsior's calculation window can vary from 10s-30s, but it's not possible to tell the exact window at this point).

Changes since v0.2.1

• ⚠️ flag names have changed significantly. See #113 for more information
• ⚠️ Prometheus metrics about metrics-server health have changed names and types
• ⚠️ / 🎉 use the secure Kubelet port with auth by default. Use of the insecure port is deprecated and may be removed as soon as next release.
• ⚠️ / 🎉 source usage rate from Kubelet directly This should improve metrics reliability, but means that the scrape interval no longer has any relation to the metrics calculation window (which is now effectively between 10-30s).
• ⚠️ / 🎉 node addresses are now chosen with the same mechanics as kube-apiserver, and can be customized with an identically named flag. This should not affect most installations, but should make it easier to work with clusters with many different node addresses, and makes metric-server more consistent with the rest of kubernetes
• 🎉 support IPv6 kubelet addresses
• 🐛 avoid passing bearer token to insecure port

v0.3.0 (alpha 1)

⚠️ This release has significant changes, including new flag names. You may need to update your deployment configurations if you've set any flags. See #113 for more information ⚠️

Changes

• ⚠️ flag names have changed significantly. See #113 for more information
• ⚠️ Prometheus metrics about metrics-server health have changed names and types
• ⚠️ / 🎉 use the secure Kubelet port with auth by default. Use of the insecure port is deprecated and may be removed as soon as next release.
• ⚠️ / 🎉 source usage rate from Kubelet directly This should improve metrics reliability, but means that the scrape interval no longer has any relation to the metrics calculation window (which is now effectively between 10-30s).
• ⚠️ / 🎉 node addresses are now chosen with the same mechanics as kube-apiserver, and can be customized with an identically named flag. This should not affect most installations, but should make it easier to work with clusters with many different node addresses, and makes metric-server more consistent with the rest of kubernetes
• 🎉 support IPv6 kubelet addresses
• 🐛 avoid passing bearer token to insecure port

Release v0.2.1

Expose apiserver metrics at /metric endpoint

The image is available as gcr.io/google_containers/metrics-server-amd64:v0.2.1.

Release v0.2.0

Support for metrics api in v1beta1.

The image is available as gcr.io/google_containers/metrics-server-amd64:v0.2.0.