Skip to content

v0.7.0
Compare
Choose a tag to compare
@pintohutch pintohutch released this 09 Jun 17:41
· 447 commits to main since this release
v0.7.0
5c354e9
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

We have just released version v0.7.0 of our managed collection for Kubernetes and v2.35.0-gmp.5-gke.0 of self-deployed collection.

Users who deploy managed collection using kubectl should reapply the manifests in the documentation. Users who deploy the service using gcloud or the GKE UI are already upgraded on clusters running version 1.25 or newer. Self-deployed collection users should upgrade their binaries to use gke.gcr.io/prometheus-engine/prometheus:v2.35.0-gmp.5-gke.0.

Changes in managed collection v0.7.0:

  • [FEATURE] PodMonitoring and ClusterPodMonitoring now can be configured to display statistics and samples of active targets in its status field, which is useful to determine whether scrape failures might be caused by malformed scrape configs that match no targets. See the documentation for how to use the target status report.
  • [FEATURE] Support for ingestion and querying of Prometheus exemplars, which allow you to correlate histogram metrics (such as a distribution of latencies) with traces. See the documentation for how to use exemplars.
  • [ENHANCEMENT] Support for multi-arch builds (both AMD64 and ARM64 node architectures are now supported).
  • [ENHANCEMENT] Remedy GKE security posture alerts so all containers run as non-root.
  • [BUGFIX] Handle exporters that write histogram series out-of-order.
  • [ENHANCEMENT] Deprecated v1alpha1 CRDs.
  • [BUGFIX] Fix a bug to tolerate if the managed alert manager is deployed with a pod IP address that is not part of RFC 6890 with a default route.
  • [ENHANCEMENT] Re-format user agent to auto-discover operating environment.
  • [BUGFIX] Fix stand-alone rule-evaluator init container bug
  • [BUGFIX] Fix config-reloader bug to mitigate Prometheus collectors transient crash looping on startup
  • [ENHANCEMENT] Clean-up and refactor some collector “self-metrics”.
  • [BUGFIX] Allow Prometheus to default to “replace” when RelabelingRule.Action is unspecified, as per the docs.
  • [ENHANCEMENT] Added safeguard checks to our webhooks to reject empty secret names
  • [ENHANCEMENT] Remove CPU limits to prevent underutilizing CPU cycles

Changes in self-deployed collection v2.35.0-gmp.5-gke.0:

  • [FEATURE] Support for ingestion and querying of Prometheus exemplars, which allow you to correlate histogram metrics (such as a distribution of latencies) with traces. See the documentation for how to use exemplars.
  • [ENHANCEMENT] Support for multi-arch builds (AMD64 and ARM64 node architectures are now supported).
Assets 2
Loading