-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Monitoring labels aren't applied to rook-ceph-exporter #13774
Comments
Poking at the code today to see if I could fix this, looks like it's already possible.
These labels are applied to both the rook/pkg/operator/ceph/cluster/nodedaemon/exporter.go Lines 264 to 265 in 6ce7b1f
We could also apply the monitoring labels, but not sure it's worth it. |
At a minimum, maybe an I think our expectation was that the (If there's ever an non-backwards compatible change to the CephCluster object, it might be interesting to move the monitoring labels into the spec.monitoring stanza or even embed a ServiceMonitorSpec there for override purposes. But the existing system works.) |
the labels listed under the 'monitoring' section are currently only being applied to the rook-ceph-mgr ServiceMonitor. This change extends those labels to also include the rook-ceph-exporter ServiceMonitor. Fixes: rook#13774 Signed-off-by: Redouane Kachach <rkachach@redhat.com>
the labels listed under the 'monitoring' section are currently only being applied to the rook-ceph-mgr ServiceMonitor. This change extends those labels to also include the rook-ceph-exporter ServiceMonitor. Fixes: #13774 Signed-off-by: Redouane Kachach <rkachach@redhat.com> (cherry picked from commit 10e2670)
+1! |
Is this a bug report or feature request?
Deviation from expected behavior:
The monitoring labels aren't applied to the
rook-ceph-exporter
service monitor.Expected behavior:
The
rook-ceph-exporter
would have the same labels applied as therook-ceph-mgr
service monitor.How to reproduce it (minimal and precise):
Add this to the cluster spec:
and notice the label only being applied to two of the three service monitors.
The text was updated successfully, but these errors were encountered: