travisn a1fc70f2fc exporter: dont delete exporter service on daemon deletion ...

The exporter service and service monitor should not
be deleted if an individual daemon is being removed
from a node. As long as the exporter is enabled with
v18 and newer, the exporter service and service monitor
should exist. Clusters were seeing their metrics stop
collection when the exporter service and service monitor
would disappear, especially when multiple clusters are
configured.

Signed-off-by: travisn <tnielsen@redhat.com>

2024-01-30 16:23:10 -07:00

..

add_test.go

core: refactor crash collector for more node daemons

2022-12-09 16:57:05 -07:00

add.go

core: report node metrics using ceph telemetry

2023-11-16 19:13:22 +05:30

crash_test.go

core: report node metrics using ceph telemetry

2023-11-16 19:13:22 +05:30

crash.go

core: report node metrics using ceph telemetry

2023-11-16 19:13:22 +05:30

exporter_test.go

exporter: bind to all interfaces if IPv6 is enabled

2023-09-12 11:39:46 -06:00

exporter.go

exporter: change deployment strategy to Recreate

2023-11-27 15:20:25 +05:30

keyring_test.go

exporter: run exporter with specific keyring

2023-11-21 23:52:50 +05:30

keyring.go

exporter: run exporter with specific keyring

2023-11-21 23:52:50 +05:30

pruner_test.go

core: refactor crash collector for more node daemons

2022-12-09 16:57:05 -07:00

pruner.go

core: import packages only once

2023-09-16 13:40:17 +08:00

reconcile.go

exporter: dont delete exporter service on daemon deletion

2024-01-30 16:23:10 -07:00