i have this problem. Is it really worth it to improve the UX and tooling of running etcd clusters? Wouldn't you rather just get rid of it? I have all the technology to just run k8s on a managed database.
-
This Tweet is unavailable.
-
K3s uses SQLite which may be good for that use case (IDK). It is more that without the plugable model no one can step in a build or try anything else. With CSI, CNI, CRI users can pick and choose what works best.
Some things need to be right from the beginning because they are infeasible to change. Other things can wait. None of CRI, CNI, CSI, API aggregation, CRD, admission webhooks, etc. existed at the beginning of the project. It's a gradual process of creating the plugin APIs.
