Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Alternatively the K3s authors could have embedded a single node etcd process into Kubernetes using the embed package instead of introducing sqlite.

https://godoc.org/github.com/etcd-io/etcd/embed

This is something the Kubernetes community might consider as well.



Yeah, OpenShift did this from the very first version. It worked pretty well. Memory use was very reasonable from etcd 3.0 on.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: