elara
etcd-compatible config store for Kubernetes with UI, RBAC, schema validation, and consumer observability.
Ficha actualizada 23 sept 2026, 13:07 · upstream 23 sept 2026, 12:57 · release elara-0.5.0
Qué es elara
Descripción editorial construida a partir del repositorio, su documentación y sus señales de mantenimiento.
Elara is a Kubernetes service that speaks the etcd v3 wire protocol, so your services keep reading config with their existing etcd client — no new SDK needed. On top of that store it adds full operator WebUI, JSON Schema validation per path pattern, groups-based RBAC, and a consumer view showing which pod reads which key at which revision. One binary, one bbolt file, no cluster to run.
Key features include drop-in compatibility with etcdctl and any etcd SDK, guardrails that reject invalid config before storage via JSON Schema validation, and an operator-friendly interface for browsing, editing, diffing, and auditing configuration across namespaces.
- Deploy Kubernetes applications using a declarative config store backed by etcd v3
- Validate application configuration against defined schemas before applying to cluster
- Monitor which pods are consuming specific config keys for observability
- Implement RBAC policies scoped per namespace or group with Casbin authorization
- Run automated config migrations and rollouts using versioned key paths
- Drop-in etcd v3 compatibility — existing clients connect unchanged without SDK changes
- JSON Schema validation at write time rejects invalid configs before storage
- Groups-based RBAC with Casbin enables fine-grained authorization per namespace
- Consumer view shows which Kubernetes pod reads each key and at what revision
- Full version history with side-by-side diff for configuration auditing
- Single-instance deployment due to bbolt exclusive file lock — no high availability out of the box
- No online backup mechanism available yet; manual backup required before restart
- Schema validation is static and does not adapt to runtime changes in config values
- Limited support for complex nested structures beyond JSON Schema constraints
Capturas del proyecto
Imágenes reales detectadas en la documentación del repositorio.
Perfil de infraestructura
Estimación inicial derivada del repositorio y de los servicios detectados.
Despliegue detectado
Qué señales reales de instalación hemos encontrado.
Deploy via Helm chart: `helm install elara elara/elara`. Use the demo build with `--build-arg DEMO_MODE=true` to seed sample namespaces, keys, schemas, and simulated k8s consumers. For production, configure ingress, persistent storage (e.g., PostgreSQL or S3), resource limits, and enable RBAC domains per namespace. The etcd-compatible API is available at port 2379 alongside the HTTP UI on port 8080.
Stack y dependencias
Componentes inferidos a partir de manifests, configuración y documentación.
Puede sustituir a
Relaciones detectadas por el análisis del repositorio y su categoría.
Experiencia real de la comunidad
Ayuda a contrastar la estimación automática con instalaciones reales.
Todavía no hay datos comunitarios para este proyecto.