Support NATS backend via websocket protocol

[lynic]

Besides nats:// protocol, NATS server also support ws:// or wss:// protocol.

I'm wondering is there any plan to support nats websocket protocol?

kine/pkg/drivers/nats/config.go

Line 160 in 59c88f9

connBuilder.WriteString("nats://")

[brandond]

Is there a difference, or is it just a different uri scheme for the same wire protocol?

[lynic]

It's just another uri scheme, just replace "nats://" with "ws://" or "wss://" in client side.
https://docs.nats.io/running-a-nats-service/configuration/websocket
https://nats.io/blog/getting-started-nats-ws/

[brandond]

ok but it could be sql or etcd over websockets as well. websockets is just the transport. I don't think ws/wss is sufficient to uniquely identify it as nats so I would not really want to add it as an alias, if it already works as-is.

[lynic]

Yes, ws/wss is not unique. Is it possible to use "nats-ws://" and "nats-wss://" for alias?

[brandond]

But why?

[lynic]

The background is that I setup a k3s with traefik, and installed k3s server on it, but I didn't expose NATS 4222 port, but instead expose nats-server websocket service via traefik ingress, it requires the client to use ws:// or wss:// to connect.

If I want to setup another k3s service and want to use NATS server as backend, it needs to point the db endpoint to ws:// or wss:// .

[brandond]

Why does it require that? The server has no idea what scheme you used to connect to it.

[lynic]

The server needs to understand the schema, it supports "nats://" , "ws://" and "wss://", to setup the nats server , needs to specific enable websocket support.
And the client side needs to use "ws://" or "wss://" protocol instead of "nats://".
Hence if I want to use this nats-server as database, the kine needs to set scheme to "ws://" or "wss://" instead of "nats://" .