newrelic-infrastructure-3.2.0

A Helm chart to deploy the New Relic Kubernetes monitoring solution

newrelic-infrastructure-3.1.1

A Helm chart to deploy the New Relic Kubernetes monitoring solution

v3.1.0

What's Changed

• chore(deps): bump aquasecurity/trivy-action from 0.2.1 to 0.2.2 by @dependabot in #355
• controlplane/authenticator: allow to use kubernetes.io/tls secrets by @roobre in #344
• config: document options by @roobre in #363

Full Changelog: v3.0.0...v3.1.0

v2.10.0

Upgrade infrastructure-bundle to 2.8.5

• See https://github.com/newrelic/infrastructure-bundle/releases/tag/2.8.5 for more details about the upgraded integrations in this release of the infrastructure-bundle

v3.0.0

Keypoints

• Please notice that even if the architecture changes the data that is scraped and forwarded to the backend does not and therefore alerts and dashboards already created will keep working as expected.

• A great effort has been made to make the solution 100% compatible with the old one at installation time. Most of the values of the helm chart have been mapped successfully, however, there are few ones that need to be manually modified. The helm chart notes will point out if a manual intervention is needed.

Many ongoing issues have been solved, in particular:

• There is a separated component taking care of scraping KSM, therefore memory request and limits can be assigned properly to a single instance allowing a noticeable reduction in the solution footprint in the cluster.

• Control plane components can be scraped even if they are running outside the cluster (Eg GKE, AWS apiServer, Rancher controlPlane)

• The nri-kubernetes process is now the main one in the scraping container allowing improved error handling, log experience and resource management.

• The integration now leverages informers to reduce its footprint in the cluster

New features have been added

• It is now possible to change the scraping interval, to reduce costs or increase the number of data points collected

• The configuration experience has been enhanced supporting a configuration file new options. Moreover "on-change" the instances are automatically restarted to reload the config file.

• it is now possible to scrape data from external control planes

---

Notice that this release can be consider stable, however the whole solution and its installation is still in beta as specified by the nri-bundle chart version

v2.9.0

• Upgrade infrastructure-bundle to 2.8.1

  • See https://github.com/newrelic/infrastructure-bundle/releases/tag/2.8.1 for more details about the upgraded integrations in this release of the infrastructure-bundle

• 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.

v2.8.3

Changed

• Updated agent and integrations to their latest versions

v2.8.2

Changed

• Updated agent and integrations to their latest versions

v2.8.1

⚠️ Breaking changes ⚠️ (Same as 2.8.0)

• 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).

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 (#194)
• Infrastructure agent and integrations have been updated to the latest versions (#202)