This message was deleted.
# k3s
a
This message was deleted.
c
You could, sure.
We don't really expect people to poke at it with etcdctl but it should support the basics
You will probably get not implemented errors for a fair bit of stuff. Basically anything not used by Kubernetes.
c
yeah, from what I've tried, it only seems to be happy with creating/non-modifying
puts
made using
txn
, would it be safe to assume it's not much of a priority to implement the full operation suite?
c
Yeah we have no plans to make it a generic etcd replacement, we're only really interested in doing what it needs to be usable as a Kubernetes datastore.
PR would be welcome though
c
perhaps reframing the question would be more appropriate - any particular place in the codebase I should look to assess op support completeness and take hints to possibly extend it? oddly enough, upstream etcd's latency sensitivity ends up itching me more than I'd like and perhaps it'd be a good opportunity to brush up on my golang
a generic pointer in the repository's dir structure oughta do
c
The codebase is pretty small. Have you looked in https://github.com/k3s-io/kine/tree/master/pkg/server
c
only grepped through it so far, as I was figuring things out in-between, so haven't looked at it from a proper coder's perspective - I guess I might as well start, thanks!
circling back on this conversation, since I only recently got the opportunity to look closer and I've noticed that a lot of plumbing exists to support missing
RaftKV
interface functions, already is used in `Txn`s, which begs the question of: is there any non-technical reason why they're missing so far? "`-EEFFORT` to maintain that code path" might be fair enough
c
As I mentioned earlier, the only real goals of the project are to implement the bits of the API necessary for Kubernetes to function properly on top of it. We've added extra bits as it makes sense for whatever reason, but we don't really have any plans to significantly increase coverage. If we did we'd probably want to add some better conformance tests as well.
c
understood, fair enough