Skip to content

Releases: strimzi/strimzi-kafka-bridge

0.26.1

27 Jul 14:57
Compare
Choose a tag to compare

Main Changes since 0.26.0

Full list of addressed issues can be found under the 0.26.1 milestone.

0.26.1-rc1

25 Jul 15:27
Compare
Choose a tag to compare
0.26.1-rc1 Pre-release
Pre-release

Main Changes since 0.26.0

Full list of addressed issues can be found under the 0.26.1 milestone.

0.26.0

14 Jul 07:19
Compare
Choose a tag to compare

Main Changes since 0.25.0

  • Removed "remote" and "local" labels from HTTP server related metrics to avoid a big growth of time series samples.
  • Removed accounting HTTP server metrics for requests on the /metrics endpoint.
  • Exposed the /metrics endpoint through the OpenAPI specification.
  • Fixed OpenAPI 3.0 OffsetRecordSentList component schema returning proper record offsets or error.
  • Fixed OpenAPI ConsumerRecord component schema returning key and value not only as (JSON) string but even as object.
  • Fixed OpenAPI HTTP status codes returned by /ready and /healthy:
    • from 200 to 204 because no content in the response in case of success.
    • added 500 in the specification for the failure case, as already returned by the bridge.
  • Dependency updates (Vert.x 4.4.4, Netty 4.1.94.Final to align with Vert.x, Kafka 3.5.0, snakeYAML 2.0, JMX Prometheus Exporter 0.18.0, Jackson 2.14.2, OAuth 0.13.0)

Full list of addressed issues can be found under the 0.26.0 milestone.

0.26.0-rc1

12 Jul 08:53
Compare
Choose a tag to compare
0.26.0-rc1 Pre-release
Pre-release

Main Changes since 0.25.0

  • Removed "remote" and "local" labels from HTTP server related metrics to avoid a big growth of time series samples.
  • Removed accounting HTTP server metrics for requests on the /metrics endpoint.
  • Exposed the /metrics endpoint through the OpenAPI specification.
  • Fixed OpenAPI 3.0 OffsetRecordSentList component schema returning proper record offsets or error.
  • Fixed OpenAPI ConsumerRecord component schema returning key and value not only as (JSON) string but even as object.
  • Fixed OpenAPI HTTP status codes returned by /ready and /healthy:
    • from 200 to 204 because no content in the response in case of success.
    • added 500 in the specification for the failure case, as already returned by the bridge.
  • Dependency updates (Vert.x 4.4.4, Netty 4.1.94.Final to align with Vert.x, Kafka 3.5.0, snakeYAML 2.0, JMX Prometheus Exporter 0.18.0, Jackson 2.14.2, OAuth 0.13.0)

Full list of addressed issues can be found under the 0.26.0 milestone.

0.25.0

14 Mar 08:06
Compare
Choose a tag to compare

Main Changes since 0.24.0

  • Fixed printing operation log at the proper logging level.
  • Fixed sending messages with headers to the sendToPartition endpoint.
  • Added missing validation on the async query 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.25.0-rc1

11 Mar 17:35
Compare
Choose a tag to compare
0.25.0-rc1 Pre-release
Pre-release

Main Changes since 0.24.0

  • Fixed printing operation log at the proper logging level.
  • Fixed sending messages with headers to the sendToPartition endpoint.
  • Added missing validation on the async query 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

18 Jan 09:39
Compare
Choose a tag to compare

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

16 Jan 11:37
Compare
Choose a tag to compare
0.24.0-rc1 Pre-release
Pre-release

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

29 Nov 11:40
Compare
Choose a tag to compare

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

29 Nov 08:18
Compare
Choose a tag to compare

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.