out_nats: protocol info before TLS handshake

[edsiper]

When a connection is issued to a NATS server, the client receives an INFO message as soon the connection is established, e.g:

{"server_id":"e1d84d38a2c8f11f4209f079d8c82203",
 "version":"0.7.5",
 "go": "go1.5.3", 
 "host":"0.0.0.0", 
 "port":4449,
 "auth_required":true,
 "ssl_required":true,
 "tls_required":true,
 "tls_verify":true,
 "max_payload":1048576
}

so based on this information the client (out_nats) must be able to switch to TLS mode. Fluent Bit already supports TLS but we need a tweak to do:

• connect to NATS server
• parse INFO message
• if TLS is enable, use Fluent Bit I/O TLS support, otherwise raw TCP backend

[edsiper]

NATS + TLS support will come in v0.8

[edsiper]

Marking this enhancement request as "wonfix-until-requested", meaning, we will reconsider it implementation until some users really require it.

[enozcan]

we will reconsider it implementation until some users really require it.

@edsiper Hi, FWIW we got blocked by this issue where we secure NATS cluster with TLS and want to publish messages thru FluentBit.

[jm-amt]

Is TLS for the NATS output still not supported?