This message was deleted.
# k3s
a
This message was deleted.
c
what exactly did you specify as the datastore endpoint?
It looks like you just put
localhost:4222
instead of
<jetstream://localhost:4222>
as shown in the blog post you linked to?
w
nohup $Exec $Cmds $Opts --datastore-endpoint=<jetstream://localhost:4222> &> /dev/null &
c
huh I don’t think that’s even valid :/
the nats stuff has been wholly contributed by synadia, but I don’t think those docs work yet
w
Ah ok, the reference guide is where I got the method they used. Maybe something was special for their setup of NATS: Exploring NATS as a backend for k3s | NATS blog
Copy code
# Run in the background or in the foreground in a different shell.
nats-server -js &

# Point k3s to the default NATS address.
k3s server --datastore-endpoint=<jetstream://localhost:4222>
c
1.27.3 is also a little out of date. they changed the connection string a while back: https://github.com/k3s-io/kine/pull/184
w
I tried
--datastore-endpoint=<nats://localhost:4222>
before but now it works, magic of reporting it I guess.
c
also keep in mind that this is still broken for multi-server clusters
😲 1
w
Oh ok, I’ll continue with my efforts with the embedded etcd then. I was also thinking of just bringing up a MySQL datastore in podman as another option for the external datastore.
l
@worried-book-58991 it’s the performance of NATS you where looking for or simply “just” trying out things?
Asking as we run etcd … and if we can get something that’a less IOPS sensitive it would be interesting
DO anyone know of blog posts or other write-ups on the potential performance gains of running NATS JetStream over etcd on a HA K3s cluster?
w
Yes that’s correct wanted something that was more performant for an embedded environment. But also something that might be more stable, I’m not sure if that is the case or not with NATS.
I looked here: nats bench - NATS Docs but I’m sure you already saw that since it’s been done by NATS. But one can run that benchmark themselves too.
l
I find etcd super super stable… that haven’t been an issue …
and we’ve run K3s in production for 1.5 years and prepped for that 1.5 year up to production …
But, yes for the performance reason NATS JetStream might be really interesting. IF it beats out etcd.