Skip to content

v0.4.0
Compare
Choose a tag to compare
@fabxc fabxc released this 27 Apr 08:39
· 648 commits to main since this release
v0.4.0
4adcfba
  • Resources (PodMonitoring, Rules, etc.) are now available as v1Existing resources are upgraded automatically.
    • Applying v1alpha1 manifests will still work as well.
  • Scraping of kubelet and cadvisor metrics can now be enabled through the OperatorConfig (documentation)
  • Pods controlled by a DaemonSet will now contain the node name instead of the pod name in the "instance" label
    • This provides a better user experience for dashboards that template on the instance label, such as those for the node exporter. The pod name remains available through the "pod" label as well.
  • Node selectors were added to only deploy on linux/amd64 nodes
  • Reduced RBAC permissions given to the operator
  • Ensure automount of serviceaccount token in deployed pods
  • Set minimized security context in deployed pods
  • Fix bug in generated scrape configurations for numeric ports
    • This brings a new limitation imposed by the underlying Prometheus logic. If a pod has no declared ports, specifying a numeric port in a PodMonitoring will still work. If the pod has any ports declared however, numeric ports used in PodMonitorings must be declared as well. Previously the latter case worked even without declaring the numeric port, but this has an undesired edge case.
  • Fix a bug where updates to GlobalRules were not handled immediately
  • When enabling Managed Collection through the Cloud console or gcloud, the OperatorConfig is now modifiable and will no longer be reset to the default state.

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 will be automatically upgraded within a week or so. This release has no impact on self-deployed collection users.

Assets 2