sfackler/kine — explained in plain English
Analysis updated 2026-08-15 · repo last pushed 2025-12-19
Run a lightweight Kubernetes staging environment backed by a single SQLite file.
Back a Kubernetes cluster with an existing Postgres database so you can use familiar backup and maintenance tools.
Eliminate the need to set up and operate etcd for small infrastructure footprints.
Use with standard Kubernetes clusters, not just K3s, to simplify database operations.
| sfackler/kine | 000madz000/rfid-attendance | 00kaku/gallery-slider-block | |
|---|---|---|---|
| Language | — | TypeScript | JavaScript |
| Last pushed | 2025-12-19 | 2024-07-22 | 2021-05-19 |
| Maintenance | Quiet | Dormant | Dormant |
| Setup difficulty | hard | easy | easy |
| Complexity | 4/5 | 2/5 | 2/5 |
| Audience | ops devops | developer | general |
Figures from each repo's GitHub metadata at analysis time.
Requires standing up a Kubernetes cluster and pointing its API server at Kine, which involves non-trivial configuration and infrastructure setup.
Kine lets you run Kubernetes using databases you probably already have, like Postgres, MySQL, or SQLite, instead of the default option called etcd. The main benefit is simplification: instead of setting up and maintaining a separate, specialized database just to make Kubernetes work, you can lean on familiar database tools you already know and trust. Under the hood, Kubernetes constantly stores and retrieves its internal state, things like configuration details and records of what's running. Normally, it expects to talk to etcd, a purpose-built database, to do this. Kine sits in between as a translator. It receives the etcd-style requests from Kubernetes and quietly converts them into standard database operations (creating, updating, or deleting records) that Postgres, MySQL, or SQLite can understand. To Kubernetes, it looks like it's talking to its usual database, but behind the scenes, the data is actually being handled by something entirely different. This tool is aimed at people who want to run Kubernetes without the extra operational burden of managing etcd. A founder or technical lead running a small infrastructure footprint might use it to run Kubernetes on top of a SQLite file, keeping things extremely lightweight for a staging environment. A larger team might use it to back their clusters with a standard Postgres database they already operate, letting them handle backups and maintenance using tools they already have. One important tradeoff to note is that it only translates the specific pieces of the etcd API that Kubernetes actually needs. It isn't a general-purpose replacement for etcd in other contexts, it is strictly built to serve as a bridge for Kubernetes and similar systems. It can run on its own, meaning it isn't tied exclusively to K3s (a popular lightweight Kubernetes distribution), you can use it with standard Kubernetes clusters too.
Kine lets Kubernetes use databases like Postgres, MySQL, or SQLite instead of its default database, etcd. It acts as a translator so you can run clusters with infrastructure you already know.
Quiet — no commits in 6-12 months (last push 2025-12-19).
No license information was provided in the explanation.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.