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.<p>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.
I got really excited about this and then realised it's only for Kubernetes: the one platform I've never believed you should deploy a database to (relational or otherwise.) I guess there are some use cases for such a deployment, but after 20 years of experience across many organisations on three continents, I've never encountered a situation that involves constantly rolling forward the database engine. Bring the engine inline with updates, sure, but weekly? Even monthly? No.