Richard Durso
Richard Durso
Bumping into this now as well. No service Monitor with ArgoCD deployed Velero.
Deployed Chart `3.1.2`, these in my `values.yaml`: ``` metrics: enabled: true scrapeInterval: 30s scrapeTimeout: 10s service: annotations: {} labels: {} serviceMonitor: enabled: true autodetect: false annotations: {} additionalLabels: {} namespace:...
Fixed... `service`, `serviceMonitor` and `prometheusRule` needed to be bumped under `metrics`. Working as expected now.
@jeremych1000 - Sorry,I just saw this request. I enabled issue tracking in [my repo](https://github.com/reefland/helm-charts) if something needs to be updated again. Anyway, I updated the helm-chart and did a test...
Was having this issue in the [discussion area](https://github.com/rook/rook/discussions/13534). Hopefully this makes it into the rook-ceph release. Nice work!
When you use the `err_is_fatal=true` zrepl considers it an error condition and generates log noise that can hides real issues. I opened #715 asking for a way to have hooks...
> You need to urlencode the space to `%20`, not ` ` I only bring this up as I was testing Kromgo and Uptime Kuma badges with `shields.io` as well, and...
Would be helpful if the configuration could let us override the default attribute being used. Here are screen shots showing idle and heating in the "hvac_action" attribute.  
No, state for me is always "heat" or "cool" or "off" or "auto" depending on the mode the thermostat is set for. The "hvac_action" reflects what is happening this moment....