Tipsmark
Tipsmark
still an issue - or rather, we had to delete and re-deploy and restore data... but certainly still a problem that a simple but rare case of disk full caused...
@jouve Did you manage to recover w/o restore from backup?
And it just happened again - few hundred GB came in, disk full - cluster DEAD... it's becoming a real showstopper that one cannot recover from such a simple problem.
Splitting WAL volume to a separate disk didn't help - again database DEAD, gone - ciao... and since backup ALWAYS enables WAL archiving it's rather useless - in our case...
@quercus-carsten Not a bad idea, but it will likely not work when using VMWare CSI since we snapshot the FCD's and expansion of a VMDK is not possible when it...
@quercus-carsten so probably last comment there - the restore finally completed, a bit over 60 HOURS! the default config of barman is, at best... useless. I have no intention of...
Still not fixed? Come on....
And if you have auto sync enable in argocd for example this leads to eternal loops - I can't believe how bad this chart is, I even raised it with...
ingress bit is particularly broken - I'll also have to either create a new chart or create some make-shift ingress resources on the side.
My guess would be you need to add their plex token as well...