3 ms·
Not 100% sure that it was using scratch, but something went wrong with the persistence. The point is not to say it wasn't human error - clearly it was, but it'
by eloff 8y ago
Not 100% sure that it was using scratch, but something went wrong with the persistence.
The point is not to say it wasn't human error - clearly it was, but it's an error that wouldn't have been as easy to make without kubernetes. There's a cost to running a database on k8s that largely people ignore. That's before you start talking about backups and recovery which also get harder and require more manual work with more potential for error.