• EnglishEspañol日本語한국어Português
  • ログイン今すぐ開始

Kubernetes integration release notesRSS

February 22, 2022
Kubernetes integration v3.1.0

February 3, 2022
Kubernetes integration v3.0.0

This new version makes significant changes to the number of components that are deployed to the cluster, and introduces many new configuration options to tune the behavior to your environment. We encourage you to take a look at what's changed in full detail here.

Breaking changes

ヒント

The number and format of the metrics reported by version 3 of the integration have not changed with respect to earlier versions.

  • The format of the values.yml file has changed to accommodate the newly added configuration options. Please take a look at our migration guide to see how to change your configuration.

Changed

  • Our solution is now deployed in three components:
    • A DaemonSet to monitor the Kubelet, deployed in all nodes of the cluster.
    • A second DaemonSet to monitor the control plane, deployed in master nodes only.
    • A Deployment to collect metrics from kube-state-metrics, deployed in the same node as the latter.
  • We now offer better control for CPU and memory limits and requests, which can be now configured for the three components individually.
  • Impact of discovery and collection operations on the API server has been greatly reduced, thanks to the use of kubernetes informers.
  • Logs messages have been greatly revamped to surface problems more clearly.

Added

  • Comprehensive configuration options have been added to provide fine-grain control to how the integration discovers and connects to metric providers. Remarkably:
    • Discovery options for control plane components have been improved. You can check the details on how discovery is configured here.
    • It is now possible to collect metrics from control plane components running outside of the cluster.
    • Discovery options for KSM and the kubelet have also been added.
  • The interval at which metrics are collected is now configurable.

January 19, 2022
Kubernetes integration v2.9.0

Changed

  • Moved default config.sample to V4, added a dependency for infra-agent version 1.20.0

Please notice that old V3 configuration format is deprecated, but still supported.

December 16, 2021
Deprecation notice: Kubernetes

Effective Monday, 1 January 2022, our Kubernetes integration drops support for Kubernetes v1.15 and lower. The Kubernetes integration v2.8.0 and higher will only be compatible with Kubernetes versions 1.16 and higher. For more information, read this note or contact your account team.

Background

Enabling compatibility with the latest Kubernetes versions and adding new features to our Kubernetes offering prevents us from offering first-class support to versions prior to v1.16.

What is happening?

  • The latest Kubernetes version v1.22 has API incompatibilities with versions prior to v1.16.
  • Most major Kubernetes cloud providers have already deprecated v1.15 and lower.

What do you need to do?

It's easy: Upgrade your Kubernetes clusters to a supported version.

What happens if you don't make any changes to your account?

The Kubernetes integration may continue to work with end-of-lifed versions. However, we can't guarantee the quality of the solution as new releases may cause some incompatibilities.

Note that support requests regarding these end-of-lifed versions won't be accepted.

November 22, 2021
Kubernetes integration v2.8.3

Changed

  • Updated agent and integrations to their latest version

November 8, 2021
Kubernetes integration v2.8.2

Changed

  • Updated agent and integrations to their latest versions

September 28, 2021
Kubernetes integration v2.8.1

Breaking changes

  • With the addition of Kubernetes 1.22.x support, we are phasing out of the support bracket Kubernetes versions 1.15.x and below. This means the supported versions bracket for this version and the rest of the nri-kubernetes 2.8.x branch is from Kubernetes v1.16.x to v1.22.x.
  • Users may still use previous versions of the integration and their Helm charts to instrument their clusters, and limited support will be offered for them. Development for said older versions is considered stopped and New Relic does not guarantee feature parity or bugfixes (security or otherwise) for those older versions.

Changed

  • Node status and conditions are now fetched from the API Server rather than KSM, which fixes some inconsistencies in the samples. This does not change which data is reported, and should be an invisible change. (#194).
  • Add a series of parameters which allow to configure a jitter to be applied to API Server response caching, which might help to spread the load on large clusters. (#185).

September 20, 2021
Kubernetes integration v2.7.1

Fixed

  • Node status and conditions are now fetched from the Kubernetes API rather than KSM, which makes the query experience more consistent.
  • Infrastructure agent and integrations have been updated to the latest versions.

August 3, 2021
Kubernetes integration v2.7.0

Added

  • Integration now reports node status and conditions as condition.{Name} (for example condition.Ready, condition.PIDPressure).
  • Added the new KubeStateMetricsNamespace parameter to restrict discovery of KSM pod to a particular namespace.
    • This should help reduce load in the control plane for clusters with many pods and/or nodes.
  • Added the unschedulable metric to K8sNodeSamples.
  • Added the podIP metric to K8sPodSample.

June 7, 2021
Kubernetes integration v2.6.0

Changed

Copyright © 2024 New Relic株式会社。

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.