<story><title>Percona Everest: open-source automated database provisioning and management</title><url>https://docs.percona.com/everest/index.html</url></story><parent_chain></parent_chain><comment><author>cyrnel</author><text>Most of the pain of running databases in k8s is all of the &amp;quot;day 2&amp;quot; operations like backups, clustering, scaling, upgrading, tuning, etc., so I&amp;#x27;m glad to see all that accumulated knowledge built into controllers like this.&lt;p&gt;One feature I feel is lacking is better handling of database credentials. I see there&amp;#x27;s a &amp;quot;copy to clipboard&amp;quot; button next to the password, which tells me we&amp;#x27;re still using the same single, static, plain-text DB passwords that we&amp;#x27;ve been using since the 90s. I&amp;#x27;d love to see some kind of cross-platform RBAC system that uses rotating credentials or asymmetric crypto or something.</text></comment>
<story><title>Percona Everest: open-source automated database provisioning and management</title><url>https://docs.percona.com/everest/index.html</url></story><parent_chain></parent_chain><comment><author>movedx</author><text>I got really excited about this and then realised it&amp;#x27;s only for Kubernetes: the one platform I&amp;#x27;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&amp;#x27;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.</text></comment>