v40

Release Highlights

• ✨ Feature Improvement: This release adds a new property nats.write_deadline to allow the operator to configure the maximum number of seconds the server will block when writing. Thanks @axel7born!
• 🐛 Bug fix: v39 would fail to deploy for deployments that configured nats.machines (rather than using BOSH links). This release fixes that regression. Thanks @andrew-edgar!

✨ Built with golang 1.16.5.

v39

• The NATS monitor port is now open on both the instance IP, as well as localhost, so that co-located jobs can easily access the metrics and forward them to, for example, a time series database.

• When setting the nats.machines to override the list of IPs (or domain names), it is now possible to add routes for both TLS and non-TLS servers by setting the new nats.tls_cluster_port and nats.nontls_cluster_port properties on the nats and nats-tls jobs respectively.

Job	Property	v38 Default	v39 Default
nats	nats.tls_cluster_port	Did Not Exist	No Default
nats-tls	nats.nontls_cluster_port	Did Not Exist	No Default

✨ Built with golang 1.15.5.

v38

Release Highlights

• ✨ Feature Improvement: mark nats and nats-tls jobs unhealthy if TCP connect fails. Now anyone using BOSH health-monitor will get a heads up that this NATS server is failing partially or fully.

v37

Release Highlights

• In this release we made changes to the default spec values for backwards compatibility with broken nats-tls client. Now the nats.no_advertise property on the nats jobs is false by default. This gives all nats-tls clients the ability to downgrade to use nat if needed.

Job	Property	v36 Default	v37 Default
nats	nats.no_advertise	true	false

• ⚠️ Warning⚠️ This change in property defaults means that you may tell your clients to use nats_tls, but they can still use nats. This means that all the traffic you think is encrypted might not be. We plan on changing this value back to "true" in the future once we fix our clients.

v36

Release Highlights

• 🐛 Bug fix: This release fixes the following issues where nats clients were attempting to connect to nts-tls servers. This release gives the operator the ability to set "no_advertise: true" on nats clusters. This will prevent the servers from sharing all peers to their clients. #25

• ⚠️ Warning⚠️ If nats-tls clients are misconfigured and relying on the ability to downgrade to nats then using these default properties will break the client. In order to be backwards compatible with broken clients that need to downgrade, you can set nats.no_advertise: false on the nats job. This means that all clients will learn about nats and nats-tls clients will have the ability to downgrade to nats if they are misconfigured.

Job	Property	v35 Default	v36 Default
nats	nats.no_advertise	Did Not Exist	true
nats-tls	nats.no_advertise	Did Not Exist	true

v35

Release Highlights

• Bug Fix: This version is built with Go 1.15.2.
• The previous version Go 1.14.1. This version of golang has the following CVE: golang/go#38070

v34

Release Highlights

• Bug Fix: Operators can deploy multiple instances of the NATs VM (with or without nats-tls enabled) and not encounter split-brain errors. More details here
• Built with Go 1.14.1

v33

Release Highlights

• Enhancement: Operators can configure nats-tls with hostnames instead of just IPs. Jobs nats and nats-tls provide hostname on links. See the
  example-manifests/ops-files/enable_nats_tls_for_cf.yml for an example working configuration with a bosh-dns-alias.
• Golang Upgraded to Go1.13.7

v28

• Golang Upgraded to 1.13.3
• Add NATS TLS job.
  *This is a separate job to allow for a migration path for clients to gradually update. See #162026712 for more information.

v27

• golang upgraded to 1.12.5