Looks like a trend for cloud-providers. When I looked into this 1+ year ago, you had three options: a) fork apiserver library + publish your build of kube-apiserver; b) expose your DBaaS with etcd3 gRPC api; c) implement your own kube-apiserver & aggregated friends.https://twitter.com/khenidak/status/1072275855991132160 …
-
Curious to learn about details, if they'll ever be shared with the community. Last time I checked, revisiting the storage layer of the apiserver library was a no-go for sig-apimachinery. Did it change
@originalavalamp@bgrant0607@the_sttts?
Has not changed. We only recently got everyone off etcd2. There are changes that need to be made to the storage layer before a stable API can be designed. Most people are using CRDs for storage for extensions.
-
-
My tweet was badly worded. I should have said "*may* get replaced at some point*". I don't know much about the details above what
@rakyll was saying and I think that's mostly a PoC or experiment. We're still using etcd AFAIK. As@bgrant0607 says, the work required is significant. -
The point was, it's an implementation detail.
- Show replies
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.