Vector v0.21.1 release notes
Upgrading Vector
When upgrading, we recommend stepping through minor versions as
these can each contain breaking changes while Vector is pre-1.0.
These breaking changes are noted in their respective upgrade
guides.
This patch release contains a few fixes for regressions in 0.21.0.
Note: Please see the release notes for v0.21.0 for additional changes if upgrading from
v0.20.X. In particular, the upgrade guide for breaking changes.
Vector Changelog
8 bug fixes
- Vector no longer panics when reloading configuration that results in added components.
- Vector no longer emits spurious
TRACElevel logs tointernal_logswhenevervector topis run. - The
kubernetes_logsno longer panics whenever an error is received from the Kubernetes API watch stream. - The
elasticsearchsink now correctly works again when using AWS authentication to send data to AWS OpenSearch. Previously the security token was not included when signing the requests. - The
natssource and sink authentication options are now configurable. Previously Vector was not correctly deserializing them. - AWS components now correctly pass the configured region to AWS STS when
assume_roleis used. This was a regression during the switch to the new Rust AWS SDK. - The
aws_cloudwatch_logssink now correctly retries throttled requests again. This was a regression during the switch to the new Rust AWS SDK. - Vector no longer panics when used with configuration options that take event paths such as
encoding.only_fields.