State management
radu-matei opened this issue · 3 comments
radu-matei commented
Investigate the addition of a state management cluster that manages the state of the tool. Decide what to support from:
- etcd
- Consul
- Redis
- alternatives (Zookeper, Memcached...?)
Ideally:
- state should be something you can opt in / out
- connection with the state management cluster is exclusively between the cluster and the server (
ktkd, or whatever the name you choose) - the client (web or CLI) gets the state through the server
- the state management cluster should be deployed, if a flag is present, at init, or later added as command from client
- to investigate the deployment of an the state management cluster on Kubernetes (Helm or a plain Kubernetes deployment? - at the moment we don't have a Helm client available, should be added - on server?)
At first, etcd will probably be the only one supported.
radu-matei commented
Work started in #21
mumoshu commented
Could we also support k8s configmaps and/or secrets as backends?
radu-matei commented
My thoughts precisely, have a look at #26
We should probably only have one issue to track these...