bitfisher
bitfisher
Sorry for the late response. I've missed your comment :( Glad to hear, that there is some progress. We are still stuck to k8s < 1.22 here :( BTW ......
Are there any updates or plans when this separate package will be available?
same here on bare-metal x86_64 with fresh hdd
Maybe related to #13564
Hi @sp98 ! OSD.21 was set to `/dev/sde` although storage config was set to `/dev/disk/by-id/scsi-350000f007424edf0`. `/dev/disk/by-id/scsi-350000f007424edf0` pointed to `/dev/sde`. After node reboot `/dev/disk/by-id/scsi-350000f007424edf0` points to `/dev/sdd`.
This is exactly what i did, to solve this issue! delete OSD deployment -> restart rook operator -> operator recreates OSD deployment with `ROOK_BLOCK_PATH` correctly set
Just came across this because we'd need monitoring using `Prometheus` with `PodMonitor` too. I believe that's a very common use-case for monitoring/alerting in k8s. It's not clear to me if...
At the moment i'm using sidecar and podmonitor to achieve prom scraping. ```yaml ... sidecars: - name: metrics image: percona/mongodb_exporter:0.47.1 securityContext: runAsNonRoot: true allowPrivilegeEscalation: false capabilities: drop: - ALL resources:...
Hi @MSDarwish2000, we've also ran into this! A bugfix release would be very helpful! It seems to happen also when using `FIFO` instead of `LRU`.