i have this problem. Is it really worth it to improve the UX and tooling of running etcd clusters? Wouldn't you rather just get rid of it? I have all the technology to just run k8s on a managed database.
-
This Tweet is unavailable.
We need to spec out desired watch semantics (e.g., the consistency model) and storage layout changes before we expose a pluggable storage API.https://github.com/kubernetes/kubernetes/pull/31622#issuecomment-327606218 …
-
-
Unfortunately there just isn't enough motivation to do that. Everybody is just going to implement "Just enough etcd API" to make k8s work. Shortest path.
-
I think it's a matter of priorities for the sig owning API-machinery, right
@bgrant0607?
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.