Skip to content
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

Consider replacing etcd with sqlite #312

Closed
pierreozoux opened this issue Feb 9, 2019 · 7 comments
Closed

Consider replacing etcd with sqlite #312

pierreozoux opened this issue Feb 9, 2019 · 7 comments
Labels

Comments

@pierreozoux
Copy link

pierreozoux commented Feb 9, 2019

In relation to #303 to save more memory, and like in k3s project, we could think of reducing the memory footprint by using SQLite.

What do you think about the idea?

@pierreozoux pierreozoux changed the title replace etcdv2 with sqlie Consider replacing etcd with sqlite Feb 9, 2019
@ktsakalozos
Copy link
Member

This is a direction we would like to explore. There are many benefits in using SQLite in the place of etcd, both interms of performance and maintenance. We could even use a distributed version of SQLite https://github.com/CanonicalLtd/dqlite . For sure a very interesting goal to pursue. Again, are you @pierreozoux or any one else willing to lead this effort?

@ghost
Copy link

ghost commented Feb 27, 2020

rancher/k3s actually provides this functionality via https://github.com/rancher/kine I believe. Perhaps this could be helpful?

@ktsakalozos
Copy link
Member

Dqlite is coming really soon. Have a look at this: sudo snap install microk8s --classic --channel=edge/test-dqlite

@ghost
Copy link

ghost commented Feb 27, 2020

Nice. Is this being done via kine or another layer?

@ktsakalozos
Copy link
Member

It is not using kine. Have a look at https://github.com/ubuntu/microk8s/tree/feature/ha-dqlite

@balchua
Copy link
Collaborator

balchua commented Sep 21, 2020

This is now the default for 1.19 MicroK8s.

@stale
Copy link

stale bot commented Aug 18, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the inactive label Aug 18, 2021
@stale stale bot closed this as completed Sep 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants