This message was deleted.
# rke2
a
This message was deleted.
m
If it's a service that had a pod very recently created, it could be that the pod just isn't up yet, in which case, this is benign, assuming it eventually goes away.
c
Everything has been up for a few days now and I’ve tried to reinstall rancher-monitoring with helm. Same result. 😞 I wish the error was a little more verbose
Boils down to
Copy code
ts=2023-08-10T23:26:27.849Z caller=main.go:924 level=error msg="Error reloading config" err="couldn't load configuration (--config.file=\"/etc/prometheus/config_out/prometheus.env.yaml\"): parsing YAML file /etc/prometheus/config_out/prometheus.env.yaml: relabel configuration for replace action requires 'target_label' value"
Although I didn’t see any replace action rule in the config file.. Soon as I disable the pushprox nodes
Copy code
## rke2 PushProx Monitoring
# rke2ControllerManager:
#   enabled: true
# rke2Etcd:
#   enabled: true
# rke2Scheduler:
#   enabled: true
Prometheus is happy again.
159 Views