Closed tommyjcarpenter closed 4 months ago
Dupe of #772
Right now the config.leafnodes.enabled
turns on the server portion. If all you need is remotes leave config.leafnodes.enabled=false
, you should be able to workaoround with something like this:
config:
merge:
lefanodes:
remotes:
- url: xxx:7222
account: ...
credentials: ...
Since you can put any valid nats.conf
into config.merge
@caleblloyd that still leaves:
[7] 2024/04/26 23:19:40.432725 [ERR] Error trying to connect as leafnode to remote server ":7422" (attempt 1): lookup for host "": lookup : no such host
because it gets merged in with the default parameters..
What motivated this proposal?
i dont see how its possible to form a config that looks like this:
without adding a port, so that this server itself does not allow leaf connections.
I have tested that this works, without helm.
even explicitly setting to null:
doesnt work:
the relevent template is here: https://github.com/nats-io/k8s/blob/main/helm/charts/nats/files/config/leafnodes.yaml#L2
What is the proposed change?
maybe move
port
under a flag likeif allowConnections
?Who benefits from this change?
No response
What alternatives have you evaluated?
No response