Releases: cloudfoundry/loggregator-release
Loggregator 78
Important Note
This version of Loggregator restricts ciphers to use only the following 4 ciphers. This is a breaking change for some operators and a configurable property for opting into more cipher suites was introduced in Loggregator 85
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
New Features
- When requesting recent logs, a
limit
param can set to return the mostn
most recent log lines - Updated README.md with useful information about loggregator
- added instructions for syslog drain binder mutual TLS requirements
Change Log
- Remove statsd-injector from loggregator and statsd-injector cert generation and moved it
to its own release - Add deployment, job, and index to Metron metrics
- statsd-injector was removed from the Loggregator repo in this release. It should now be includes as it's own release
Note: It was discovered that this release introduces an issue where if a metron or doppler dies it's corresponding component exponentially produces logs. A bug fix is planned for this issue.
Loggregator 77
Important Update to Cert Generation
- Loggregator now requires properties set for mutual auth with Cloud Controller. This is used for retrieving application names for inclusion in syslog drains and is set with the following new properties.
loggregator.tls.syslogdrainbinder.cert
: TLS certificate for syslogdrainbinder, signed by diego bbs CAloggregator.tls.syslogdrainbinder.key
: TLS key for syslogdrainbinder, signed by diego bbs CA- Use
<diego-bbs-ca.crt>
and<diego-bbs-ca.key>
when runninggenerate-loggregator-certs
. The diego BBS CA cert and key are typically generated separately from this script. - See the Loggregator README for more details on the new flag
Important Note
This version of Loggregator restricts ciphers to use only the following 4 ciphers. This is a breaking change for some operators and a configurable property for opting into more cipher suites was introduced in Loggregator 85
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
New Features
- "loggregator" has been replaced by app, org and space name for host name in syslog drains
Loggregator 76
Important Note
This version of Loggregator restricts ciphers to use only the following 4 ciphers. This is a breaking change for some operators and a configurable property for opting into more cipher suites was introduced in Loggregator 85
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Features
- Removal of statsd-injector and other refactoring
- Removal of "blobify" scripts for deploying as binaries
- Emission of new metrics for loggregator api v2 envelopes
- Addition of ring-buffer "diode" to metron
Loggregator 75
Important Note
This version of Loggregator restricts ciphers to use only the following 4 ciphers. This is a breaking change for some operators and a configurable property for opting into more cipher suites was introduced in Loggregator 85
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
New Features
- Defined v2 envelope for gRPC see Loggregator API repo
- Exposed new input into doppler using v2 Loggregator API
- Converted v2 to v1 envelopes in doppler
Loggregator 74.0.2
BUG FIXES
- Includes blobs for cf-deployment
Loggregator 74.0.1
Bug Fix
- Removed validation against extended key usage is breaking cf-deployment
Loggregator v74
Important Note
This version of Loggregator restricts ciphers to use only the following 4 ciphers. This is a breaking change for some operators and a configurable property for opting into more cipher suites was introduced in Loggregator 85
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Bug Fixes:
- Fixed an issue when metron failsover to UDP if provided with invalid certs. TrafficController and Doppler no longer panic if provided with invalid certs.
- Corrected faulty use of
--debug
flag frommetron_agent_windows
job. - As part of validating certs we erroneously assume certs should have clientAuth value set for extended key usage.
Loggregator 73.0.1
BUG FIX
This minor version upgrade fixes a reference to the now deprecated debug flags.
Loggregator 73
Important Notices
We are deprecating the use of the following debug flags. These flags use the gosteno library and produce debug logs for every single log and metric event. this hides useful debug information produced without a flag. The deprecated flags are
- traffic_controller.debug
- doppler.debug
- metron_agent.debug
- syslog_drain_binder.debug
This version of Loggregator restricts ciphers to use only the following 4 ciphers. This is a breaking change for some operators and a configurable property for opting into more cipher suites was introduced in Loggregator 85
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
New Features
- Improved deploy time by using precompiled blobs
Loggregator 72
Important Notice - New Certificates Required for gRPC Transport
In order to secure the transport of log messages going forward Loggregator will require Metron cert & key as well as the Loggregator CA cert. You won't be able to deploy the this and future versions of Loggregator if you don't have these configured. See our README with specifics for generating and setting up your certs.
Important Notice - Cipher Suite Restrictions
This version of Loggregator restricts ciphers to use only the following 4 ciphers. This is a breaking change for some operators and a configurable property for opting into more cipher suites was introduced in Loggregator 85
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Important Notice - ETCD Removal
This release removes etcd from metron. You no longer need to include etcd in your release if you are colocating metron.
New Features
- Improved service discovery for Dopplers by removing etcd from metron
- Encrypted log transport Metron->Doppler (via gRPC)
- Pooled connections from Metron->Doppler (via gRPC)
- Changed retry strategy for connecting to with etcd in doppler