-
Notifications
You must be signed in to change notification settings - Fork 359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Guidance and performance information on using database backends (mysql, postgres) #1623
Comments
Hi. Thanks. Interesting read - was not aware of it. |
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 |
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
The text was updated successfully, but these errors were encountered: