Lessons learned in using a different storage backend for Kubernetes

[pingenglj]

Hi, I find this a very interesting project and am wondering if you have a write-up or similar document somewhere with your lessons learned in supporting a different storage backend for Kubernetes.

Im using Kine as a starting point to create a no-sql driver to support other key-value databases next to etcd (ie. Riak), and it can be difficult to determine why exactly some things are not working yet while developing. Specifically, Im curious what etcd API endpoints (Watch, Lease, Deletes, Transaction..) and primitives (mod_revision, version, ...) really need to be implemented properly to get a minimal cluster up (1 master, 1 worker, 1 nginx Pod running).

Very interested in your experiences! That would also help me with estimating if this is viable in the short time available to me.

Currently I added a minimal Create, Get, Update, and List, but that does not appear to be enough:

Dec 28 20:13:04 master-1 k3s[29278]: E1228 20:13:04.326211   29278 kubelet.go:2291] "Error getting node" err="node \"master-1\" not found"

Thanks! And again, great project!