Skip to content
Projets

k3s-io/kine has 2,438 GitHub stars and 331 forks. GitHot measured 0 stars in 24 hours, +5 in 7 days, and +10 in 15 days. Last checked 2026-11-21 06:21 UTC. Last push 2026-11-18.

Comment ces chiffres sont mesurés

What you can do

  • Can be ran standalone so any k8s (not just K3s) can use Kine
  • Watcher: Watch, RequestProgress, Close
  • KV: Put, Get, GetStream, Delete, Compact, Txn
  • Cluster: MemberList

Progression mesurée des étoiles

in 24h
0
in 7 days
+5
in 15 days
+10
in 1 month
Historique en cours

Variations nettes sur des périodes qui se chevauchent, pas des totaux quotidiens. Les mesures absentes restent vides. Les étoiles indiquent l’intérêt, pas la qualité.

À propos

Run Kubernetes on MySQL, Postgres, sqlite, not etcd.

Données

README.md

Original

Kine (Kine is not etcd)

Kine is an etcdshim that provides an etcd-compatible API on top of various backend datastores:

Features

  • Can be ran standalone so any k8s (not just K3s) can use Kine
  • Implements the subset of the etcd V3 API required by the Kubernetes API server - not intendend to be usable as a generic etcd server

See an example.

High Availability

If you want to run multiple Kine instances (or multiple K3s server nodes, using the Kine embedded in K3s) you must use an external SQL database, or NATS, or T4.

  • The SQLite and Memory backends support only a single Kine instance.
  • The SQLite backend does not support use of shared-cache mode without WAL journal.
  • The SQLite backend does not support use of temporary or in-memory databases; use the Memory backend instead.
  • The SQLite backend does not not support running multiple instances against a shared DB file; either on a single host, or on shared storage mounted by multiple hosts.

Developer Documentation

A high level flow diagram and overview of code structure is available at docs/flow.md.