twz123/kine — explained in plain English
Analysis updated 2026-08-15 · repo last pushed 2024-01-10
Run Kubernetes on a laptop using a local SQLite file instead of etcd.
Point Kubernetes at an existing PostgreSQL instance to avoid managing a separate etcd cluster.
Simplify single-node Kubernetes deployments by using MySQL as the backing store.
Use K3s with a familiar database in resource-constrained environments.
| twz123/kine | 000madz000/rfid-attendance | 00kaku/gallery-slider-block | |
|---|---|---|---|
| Language | — | TypeScript | JavaScript |
| Last pushed | 2024-01-10 | 2024-07-22 | 2021-05-19 |
| Maintenance | Dormant | Dormant | Dormant |
| Setup difficulty | moderate | 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 an existing database like PostgreSQL or MySQL to configure, and the README is sparse on operational details so you'll need to study the examples and flow diagram.
Kine lets you run Kubernetes using a database you probably already have, like PostgreSQL, MySQL, or SQLite, instead of the default database Kubernetes normally requires. Normally, Kubernetes depends on a specialized database called etcd to store its internal state and coordinate the system. Kine acts as a translator in the middle: Kubernetes thinks it is talking to etcd, but Kine is actually routing those requests to a more familiar database. This matters because etcd can be a pain to operate, especially for smaller teams or single-node setups. If you'd rather just point Kubernetes at a Postgres instance or a local SQLite file, Kine makes that possible. It was originally built for K3s, a lightweight Kubernetes distribution, but it can run standalone so any Kubernetes cluster can use it. The project works by implementing just enough of the etcd API to keep Kubernetes happy. It translates the operations Kubernetes expects, create, update, delete, into equivalent calls against whichever database you've configured. The README is upfront that this is a subset of etcd's full API, so it's not a general-purpose etcd replacement, it's specifically tuned for what Kubernetes needs. Who would use this? Someone running Kubernetes in a constrained environment, a laptop, a small server, or a setup where you already have a Postgres or MySQL instance and don't want to stand up a separate etcd cluster just for Kubernetes. It's a practical tool for people who want Kubernetes but with simpler infrastructure underneath. The README is sparse on operational details, so you'd likely need to check the provided example and flow diagram to understand setup and limitations before committing to it.
Kine lets you run Kubernetes with a standard database like PostgreSQL, MySQL, or SQLite instead of etcd. It translates Kubernetes etcd API calls into operations your existing database can understand.
Dormant — no commits in 2+ years (last push 2024-01-10).
The explanation does not mention a specific license for this project.
Setup difficulty is rated moderate, 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.