Skip to content

v3.0.0

Compare
Choose a tag to compare
@paologallinaharbur paologallinaharbur released this 02 Feb 13:47
· 646 commits to main since this release
1d4c557

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