Releases: strimzi/strimzi-kafka-bridge
0.25.0-rc1
Main Changes since 0.24.0
- Fixed printing operation log at the proper logging level.
- Fixed sending messages with headers to the
sendToPartitionendpoint. - Added missing validation on the
asyncquery parameter for sending operations in the OpenAPI v3 specification. - Fixed memory calculation by using JVM so taking cgroupv2 into account.
- Dependency updates (Vert.x 4.3.8, Netty 4.1.87 to align with Vert.x, Kafka 3.4.0, OpenTelemetry 1.19.0)
- Added feature to unsubscribe topics by executing a subscribe or assign request with an empty topics list.
- Strimzi OAuth updated to 0.12.0 with support for automatic retries during authentication and token validation.
Full list of addressed issues can be found under the 0.25.0 milestone.
0.24.0
Main Changes since 0.23.1
- Fixed regression about producing messages not working when CORS is enabled
- Dependency updates (Netty 4.1.86.Final)
- Refactored producer, consumer and admin endpoints by using the Apache Kafka client API instead of the Vert.x one
- Removed the usage of the Vert.x Config component for reading the bridge configuration
- Replaced the Vert.x JSON handling with Jackson
Changes, deprecations and removals
Support for bridge.tracing=jaeger tracing based on Jaeger clients and OpenTracing API was deprecated in the 0.22.0 release.
As the Jaeger clients are retired and the OpenTracing project is archived, we cannot guarantee their support for future versions.
In the 0.22.0 release, we added support for OpenTelemetry tracing as a replacement.
If possible, we will maintain the support for bridge.tracing=jaeger tracing until June 2023 and remove it afterwards.
Please migrate to OpenTelemetry as soon as possible.
Full list of addressed issues can be found under the 0.24.0 milestone.
0.24.0-rc1
Main Changes since 0.23.1
- Fixed regression about producing messages not working when CORS is enabled
- Dependency updates (Netty 4.1.86.Final)
- Refactored producer, consumer and admin endpoints by using the Apache Kafka client API instead of the Vert.x one
- Removed the usage of the Vert.x Config component for reading the bridge configuration
- Replaced the Vert.x JSON handling with Jackson
Changes, deprecations and removals
Support for bridge.tracing=jaeger tracing based on Jaeger clients and OpenTracing API was deprecated in the 0.22.0 release.
As the Jaeger clients are retired and the OpenTracing project is archived, we cannot guarantee their support for future versions.
In the 0.22.0 release, we added support for OpenTelemetry tracing as a replacement.
If possible, we will maintain the support for bridge.tracing=jaeger tracing until June 2023 and remove it afterwards.
Please migrate to OpenTelemetry as soon as possible.
Full list of addressed issues can be found under the 0.24.0 milestone.
0.23.1
Main Changes since 0.23.0
- Dependency updates (Netty 4.1.85.Final)
Full list of addressed issues can be found under the 0.23.1 milestone.
0.23.0
Main Changes since 0.22.3
- Moved from using the Jaeger exporter to OTLP exporter by default
- Moved to Java 11 at language level, dropped Java 8 and use Java 17 as the runtime for all containers
- Fixed bug about missing OAuth password grants configuration
- Dependency updates (Vert.x 4.3.5)
- Dependency updates (snakeYAML CVE-2022-41854)
- Add Oauth metrics into the
jmx_metrics_config.yaml
Changes, deprecations and removals
- Since this version there is no support for AMQP 1.0 protocol anymore.
This was discussed and approved with the proposal #42
Full list of addressed issues can be found under the 0.23.0 milestone.
0.23.0-rc1
Main Changes since 0.22.3
- Moved from using the Jaeger exporter to OTLP exporter by default
- Moved to Java 11 at language level, dropped Java 8 and use Java 17 as the runtime for all containers
- Fixed bug about missing OAuth password grants configuration
- Dependency updates (Vert.x 4.3.5)
- Dependency updates (snakeYAML CVE-2022-41854)
- Add Oauth metrics into the
jmx_metrics_config.yaml
Changes, deprecations and removals
- Since this version there is no support for AMQP 1.0 protocol anymore.
This was discussed and approved with the proposal #42
Full list of addressed issues can be found under the 0.23.0 milestone.
0.22.3
Main Changes since 0.22.2
- Strimzi OAuth updated to 0.11.0 bringing support for password grants and OAuth metrics
- Fixed bug about tracing span creation missing when the consumer poll operation fails
- OpenTelemetry updated to 1.18.0
- Dependency updates (Jackson Databind)
Full list of addressed issues can be found under the 0.22.3 milestone.
This release has OpenTelemetry support by using the Jaeger exporter by default.
This exporter needs a Jaeger endpoint to send traces to.
OpenTelemetry project encourages use of the OLTP exporter and will deprecate and remove the Jaeger exporter in the future.
For this reason, the Strimzi project is going to move from the Jaeger exporter to the OTLP exporter for the next releases.
In order to use it, the minimum version of the Jaeger backend has to be 1.35 because it's the first version exposing an OLTP endpoint for getting traces from such an OLTP exporter.
When the migration is done, Strimzi users can still use the Jaeger exporter if they want by building their own image with the opentelemetry-exporter-jaeger library and setting OTEL_TRACES_EXPORTER=jaeger environment variable.
0.22.3-rc1
Main Changes since 0.22.2
- Strimzi OAuth updated to 0.11.0 bringing support for password grants and OAuth metrics
- Fixed bug about tracing span creation missing when the consumer poll operation fails
- OpenTelemetry updated to 1.18.0
- Dependency updates (Jackson Databind)
Full list of addressed issues can be found under the 0.22.3 milestone.
0.22.2
Main Changes since 0.22.1
- Enable rack-awareness when the bridge is deployed by the Strimzi operator
- Documentation improvements
- How to enable distributed tracing
- More details about using Cross-Origin Resource Sharing (CORS)
- Dependency updates (Kafka CVE-2022-34917)
- Dependency updates (Netty)
Full list of addressed issues can be found under the 0.22.2 milestone.
0.22.1
Main Changes since 0.22.0
- Dependency updates (snakeYAML CVE-2022-38752)
- Dependency updates (Kubernetes configuration provider)
Full list of addressed issues can be found under the 0.22.1 milestone.