Open sdemura opened 1 month ago
ERRO[0001] btree watcher error: context canceled
Not sure what that's about...
@bruth are you available to take a look at this?
Indeed, will check it out.
I will say that rke2 and k3s do something goofy when tls is enabled, that is inherited from etcd. It starts up once using a plaintext listener to extract encrypted bootstrap data that includes the CA certs, and then shuts down, and starts up again using the configured certs that it extracted the first time. That message is probably related to that, but I don't know if it's also related to the failure to properly configure the nats client. I'm not sure we've actually tested anything except for sqlite yet, in rke2.
Environmental Info: RKE2 Version:
Node(s) CPU architecture, OS, and Version:
Cluster Configuration:
single node
Describe the bug:
After seeing https://nats.io/blog/exploring-nats-as-a-backend-for-k3s/ I was hopeful this would work with the new Kine support, but it appears it doesn't.
Steps To Reproduce:
Running nats externally
Configure rke2 to use external, nats and explicitly set noEmbed
It appears that rke2 is ignoring the NATs paraemeter, as I'd expect
noEmbed:false
to betrue
here:Also wondering if it has to do with RKE2's use of
unixs://
instead ofunix://
for the Kine socket.