github grafana/k8s-monitoring-helm k8s-monitoring-4.3.1

3 hours ago

What's changed

  • Validate that each collector's Alloy stability level is high enough for the experimental or public-preview components in its rendered configuration. (@petewall)
  • Add connectors.spanMetrics.metricsExpiration and connectors.spanMetrics.seriesExpiration options to the Application Observability feature, so stale metrics and series can be expired instead of accumulating indefinitely. (#2875) (@petewall)
  • Add a validation that detects another Alloy Operator already running in the cluster that would compete to manage the same Alloy instances. Disable with alloy-operator.conflictCheck: false. (@petewall)
  • Update Alloy Operator to 0.6.2, kube-state-metrics to 8.0.0, Node Exporter to 4.56.1, and OpenCost to 2.5.28 (@petewall)* When the Alloy Operator is not deployed by this chart (alloy-operator.deploy: false), pin the Alloy image tag on the Alloy instances so an external (possibly older) operator does not substitute its own default Alloy image. Set image.tag on a collector to override. (@petewall)

Chart released at https://github.com/grafana/helm-charts/releases/tag/k8s-monitoring-4.3.1

Full changelog: CHANGELOG.md

Don't miss a new k8s-monitoring-helm release

NewReleases is sending notifications on new releases.