Since the cluster.authorization.timeout is set, username:password@ will be added to the cluster node URLs.
But, there are no default values for username or password, so when url-encoding the values they turn into <no value>.
The consequence of this seems to have been very chaotic coordination between cluster nodes.
Fix
I've added an extra conditional around the authorization template.
Problem
Stumbled upon an interesting, and very chaotic issue.
Installing the chart with a simple values file like this:
will be templates into a bad nats server config. The config will parse, but the generated
routes
will contain bad values:Since the
cluster.authorization.timeout
is set,username:password@
will be added to the cluster node URLs. But, there are no default values for username or password, so when url-encoding the values they turn into<no value>
.The consequence of this seems to have been very chaotic coordination between cluster nodes.
Fix
I've added an extra conditional around the authorization template.