You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
all pods are covered by some ServiceMonitor/PodLogs; metamonitoring is restricted to pod from the chart
some implicit naming conventions: to scrape PVC volumes information for metamonitoring (helm: meta-monitoring #2068) we assume that the PVCs created by the chart have a storage- prefix. If this prefix is changed in any of the StatefulSets the metamonitoring will break and stop collecting data for the volumes. We have no way of knowing this during the review process now.
Verify that all component have an attached volume under /data. The default mimir.config assumes /data is a mounted directory.
all resources have the standard kubernetes annotations (app.kubernetes.io/)
Removing the squad/customer label from this issue since this is a bit of a pet project. If you feel like this should be something that a larger group of people chip away at officially, put it on the next quarter planning spreadsheet. Creating smaller issues made from this might be another good strategy.
A follow-up on #2137
What more checks we can add:
ServiceMonitor
/PodLogs
; metamonitoring is restricted to pod from the chartstorage-
prefix. If this prefix is changed in any of theStatefulSets
the metamonitoring will break and stop collecting data for the volumes. We have no way of knowing this during the review process now./data
. The defaultmimir.config
assumes/data
is a mounted directory.The text was updated successfully, but these errors were encountered: