Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Most of the pain of running databases in k8s is all of the "day 2" operations like backups, clustering, scaling, upgrading, tuning, etc., so I'm glad to see all that accumulated knowledge built into controllers like this.

One feature I feel is lacking is better handling of database credentials. I see there's a "copy to clipboard" button next to the password, which tells me we're still using the same single, static, plain-text DB passwords that we've been using since the 90s. I'd love to see some kind of cross-platform RBAC system that uses rotating credentials or asymmetric crypto or something.



The problem is typically day 1000 problems: The database broke, nobody really understands all the stuff and dependencies by the kubernetes helm chart and still you have to fix it.

Downtime is now calculated in days and not hours.


Recover to a snapshot in one to two hours, then debug

Dump the snapshot into a managed DB short-term if you have to if the team can’t wrangle the controller


Google cloud managed postgres accepts both old school passwords and IAM users (where you never see the password, it's baked into the DB).


Same with RDS on AWS (pg and MySQL both)




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: