Guidance and performance information on using database backends (mysql, postgres)

[joaocc]

Is your feature request related to a problem?

Not a problem, but rather a lack of guidance on performance characteristics or scalability on running vcluster using database backend (mysql, postgres) as per https://www.vcluster.com/docs/deploying-vclusters/persistence#datastore-options.

Which solution do you suggest?

Provide some guidance on what to pay attention to when planning to use database as persistence layer (mysql, postgres), for the control plane (vs etcd).
At the moment there doesn't seem to be anything in the site, github or slack.

Which alternative solutions exist?

Not much

Additional context

No response

[alexandradragodan]

Hey, @joaocc
Thanks for the suggestion.

Have you taken a look here?

Let me know if that's helpful in tackling your endeavour

[joaocc]

Hi. Thanks. Interesting read - was not aware of it.
However in terms of comparison it is comparing sqlite-on-EBS with etcd-on-EBS.
I was prob not clear enough, in that I was interested on the etcd-on-mysql or etc-on-postgresql (local, serverless/aurora-v2, ...). Will fix description.
And, of course, being cheeky, etcd-on-EFS would also be interesting as comparison :) (#1342).
Thanks

[heiko-braun]

External database storage is on the roadmap and will be included in future versions. For now, only k3s seems to cover what you are looking for: https://www.vcluster.com/docs/deploying-vclusters/persistence