|
[ANNOUNCE] [RELEASE] Strimzi Kafka Operators 0.33.0
Jakub Scholz
Strimzi Kafka Operators 0.33.0 has been released. The main changes in this release include: * Support for Kafka 3.3.2 * Automatic restarts of failed Connect or Mirror Maker 2 connectors * Redesign of Strimzi User Operator to improve its scalability * Move to Java 17 * Improved FIPS support If you use Ingress listener with mTLS authentication, please check the known issues section as well! This release supports Kubernetes 1.19 and newer. Direct upgrade from Strimzi 0.22 or earlier is not supported anymore. For more details about this release and installation files, go to https://github.com/strimzi/strimzi-kafka-operator/releases/tag/0.33.0 You can also check a video about the main new features on our YouTube channel: https://youtu.be/CclPi4zp7Cs. Check out also the blog posts covering some of the new features at https://strimzi.io/blog/. Thanks to everyone who contributed to this release! Thanks & Regards Strimzi team |
|
|
|
RC1 of Strimzi Kafka Operators 0.33.0 is available for testing
Jakub Scholz
Release candidate 1 of Strimzi Kafka Operators 0.33.0 is now available for testing. The main improvements in this release include: * Support for Kafka 3.3.2 * Automatically restarts of failed Connect or Mirror Maker 2 connectors * Redesign of Strimzi User Operator to improve its scalability * Move to Java 17 * Improved FIPS support For more details, a full list of changes, and installation files, go to https://github.com/strimzi/strimzi-kafka-operator/releases/tag/0.33.0-rc1 Any feedback can be provided on the Strimzi mailing list, on the #strimzi Slack channel on CNCF Slack, or as a GitHub issue or discussion. Thanks & Regards Strimzi team |
|
|
|
[ANNOUNCE] [RELEASE] Strimzi Kafka Bridge 0.24.0
Paolo Patierno
New version 0.24.0 of Strimzi Kafka Bridge has been released.
### 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.
For more details, go to https://github.com/strimzi/strimzi-kafka-bridge/releases/tag/0.24.0
Thanks to everyone who contributed to this release!
Strimzi team
Paolo Patierno
Senior Principal Software Engineer @ Red Hat
Microsoft MVP on Azure |
|
|
|
RC1 of Strimzi Kafka Bridge 0.24.0
Paolo Patierno
Release
Candidate 1 of Strimzi Kafka Bridge the 0.24.0 is now available for testing.
###
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.
More
details and a full list of changes can be found on the GitHub release page: https://github.com/strimzi/strimzi-kafka-bridge/releases/tag/0.24.0-rc1
Any feedback can be provided on the mailing list, on Slack or as a GitHub issue.
Thanks
& RegardsStrimzi team
Paolo Patierno
Senior Principal Software Engineer @ Red Hat
Microsoft MVP on Azure |
|
|
|
[ANNOUNCE] [RELEASE] Strimzi Canary 0.6.0 released
Paolo Patierno
We have released Strimzi Canary 0.6.0.
Strimzi canary is a tool which acts as an indicator of whether Kafka clusters are operating correctly. This is achieved by creating a canary topic and periodically producing and consuming events on the topic and getting metrics out
of these exchanges.
For more details about what it does and how to use it, check the README.md file.
For more details and installation files, go to: https://github.com/strimzi/strimzi-canary/releases/tag/0.6.0
Thanks to everyone who contributed to this release!
Thanks & Regards
Strimzi team
Paolo Patierno
Senior Principal Software Engineer @ Red Hat
Microsoft MVP on Azure |
|
|
|
Re: RC1 of Strimzi Canary 0.6.0
kwall@...
I gave RC1 a spin in my test environment, all looks good. Thanks Paolo.
|
|
|
|
RC1 of Strimzi Canary 0.6.0
Paolo Patierno
*We have prepared the RC1 of the new Strimzi Canary 0.6.0
release*
For more details and installation files, go to: https://github.com/strimzi/strimzi-canary/releases/tag/0.6.0-rc1
Any feedback can be provided on the Strimzi mailing list, on the #strimzi Slack channel on CNCF Slack or as a GitHub issue.
Thanks & Regards
Strimzi team
Paolo Patierno
Senior Principal Software Engineer @ Red Hat
Microsoft MVP on Azure |
|
|
|
[PROPOSAL] Stable identities for Kafka Connect worker nodes
Jakub Scholz
I opened a new proposal for stable Kafka Connect and Kafka Mirror Maker 2 pod names which should give the worker nodes stable identities and improve the way how tasks are rebalanced when reconfiguring the Connect or MM2 clusters. If you are interested, please have a look and comment on the PR: https://github.com/strimzi/proposals/pull/69 Thanks & Regards Jakub |
|
|
|
[PROPOSAL] Updated StrimziPodSet graduation schedule
Jakub Scholz
I opened a new proposal with the updated schedule for StrimziPodSet graduation. If you are interested in this topic, you can read more and raise comments about it in the PR on GitHub: https://github.com/strimzi/proposals/pull/68 Thanks & Regards Jakub |
|
|
|
[ANNOUNCE] [RELEASE] Strimzi Kafka Bridge 0.23.1
Paolo Patierno
New version 0.23.1 of Strimzi Kafka Bridge has been released. The main changes in this release are:
* Dependency updates (Netty 4.1.85.Final)
For more details, go to https://github.com/strimzi/strimzi-kafka-bridge/releases/tag/0.23.1
Thanks to everyone who contributed to this release!
Strimzi team
Paolo Patierno
Senior Principal Software Engineer @ Red Hat
Microsoft MVP on Azure |
|
|
|
[ANNOUNCE] [RELEASE] Strimzi Kafka Bridge 0.23.0
Paolo Patierno
New version 0.23.0 of Strimzi Kafka Bridge has been released. The main changes in this release are:
* 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]
For more details, go to https://github.com/strimzi/strimzi-kafka-bridge/releases/tag/0.23.0
Thanks to everyone who contributed to this release!
Strimzi team
Paolo Patierno
Senior Principal Software Engineer @ Red Hat
Microsoft MVP on Azure |
|
|
|
RC1 of Strimzi Kafka Bridge 0.23.0
Paolo Patierno
Release Candidate 1 of Strimzi Kafka Bridge the 0.23.0 is now available for testing. The main changes since 0.22.3 are:
* 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]
More details and a full list of changes can be found on the GitHub release page: https://github.com/strimzi/strimzi-kafka-bridge/releases/tag/0.23.0-rc1
Any feedback can be provided on the mailing list, on Slack or as a GitHub issue.
Thanks & Regards
Strimzi team
Paolo Patierno
Senior Principal Software Engineer @ Red Hat
Microsoft MVP on Azure |
|
|
|
[ANNOUNCE] [RELEASE] EnvVar Configuration Provider 1.1.0 and Kubernetes Configuration Provider 1.1.0
Jakub Scholz
Kubernetes and EnvVar Configuration Providers version 1.1.0 have been released. Both versions contain updated dependencies, remove support for Java 8 and add support for Java 17. For more details, check the GitHub release page: * EnvVar Configuration Provider: https://github.com/strimzi/kafka-env-var-config-provider/releases/tag/1.1.0 * Kubernetes Configuration Provider: https://github.com/strimzi/kafka-kubernetes-config-provider/releases/tag/1.1.0 Thanks to everyone who contributed to these releases! Thanks & Regards Strimzi team |
|
|
|
RC1 of EnvVar Configuration Provider 1.1.0 and Kubernetes Configuration Provider 1.1.0
Jakub Scholz
Today, we released the Release Candidate 1 of version 1.1.0 of Kubernetes and EnvVar Configuration Providers: * Kafka EnvVar Configuration Provider: https://github.com/strimzi/kafka-env-var-config-provider/releases/tag/1.1.0-rc1 * Kafka Kubernetes Configuration Provider: https://github.com/strimzi/kafka-kubernetes-config-provider/releases/tag/1.1.0-rc1 Both versions contain updated dependencies, remove support for Java 8 and add support for Java 17. Any feedback can be provided on the Strimzi mailing list, on the #strimzi Slack channel on CNCF Slack or as a GitHub issue. Thanks & Regards Strimzi team |
|
|
|
[PROPOSAL] Deprecate and remove JMX Trans
Jakub Scholz
I opened a new proposal about deprecating and removing support for JMX Trans. If you are interested in this topic, you can read more and raise comments about it in the PR on GitHub: https://github.com/strimzi/proposals/pull/65 Thanks & Regards Jakub |
|
|
|
Strimzi OpenTelemetry support moving from Jaeger to OLTP exporter
Paolo Patierno
Hi all,
The current 0.32.0 operator and 0.22.3 bridge releases have 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.
Thanks,
The Strimzi Team
Paolo Patierno
Senior Principal Software Engineer @ Red Hat
Microsoft MVP on Azure |
|
|
|
[ANNOUNCE] [RELEASE] Strimzi Kafka Operators 0.32.0
Jakub Scholz
Strimzi Kafka Operators 0.32.0 has been released. There are some important changes in this release: * From Strimzi 0.32.0, we support only Kubernetes 1.19 and newer! * Direct upgrade from Strimzi 0.22 or earlier is not supported anymore! The other changes in this release include: * Add support for Kafka 3.3.1 and remove support for Kafka 3.1.0, 3.1.1, and 3.1.2 * Update KafkaConnector CR status so the 'NotReady' condition is added if the connector or any tasks are reporting a 'FAILED' state. * Add auto-approval mechanism on KafkaRebalance resource when an optimization proposal is ready * The ControlPlaneListener feature gate moves to GA * Add client rack-awareness support to Strimzi Bridge pods * Add support for OpenTelemetry for distributed tracing * ZookeeperRoller considers unready pods * Support multiple operations per ACLRule * Add new listener type "cluster-ip" which is using per-broker services instead of the pod DNS names For more details and installation files, go to https://github.com/strimzi/strimzi-kafka-operator/releases/tag/0.32.0 You can also check a video about the main new features on our YouTube channel: https://youtu.be/q4TXUVePRJ8 Thanks to everyone who contributed to this release! Thanks & Regards Strimzi team |
|
|
|
Re: RC1 of Strimzi Kafka Operators 0.32.0 is available for testing
kwall@...
On Sat, Oct 29, 2022 at 12:10 PM, Jakub Scholz wrote:
I gave the RC1 a spin today and encountered no issues. I was focused on the cluster operator. I tested upgraded from Kafka 3.2.3 -> Kafka 3.3.1, and the transitions between Strimzi PodSets/Statefulsets. All logs looked clean. Thank you for the work.
|
|
|
|
RC1 of Strimzi Kafka Operators 0.32.0 is available for testing
Jakub Scholz
Release candidate 1 of Strimzi Kafka Operators 0.32.0 is now available for testing. There are some important changes in this release: * From Strimzi 0.32.0, we supports only Kubernetes 1.19 and newer! * Direct upgrade from Strimzi 0.22 or earlier is not supported anymore! The other changes in this release include: * Add support for Kafka 3.3.1 and remove support for Kafka 3.1.0, 3.1.1, and 3.1.2 * Update KafkaConnector CR status so the 'NotReady' condition is added if the connector or any tasks are reporting a 'FAILED' state. * Add auto-approval mechanism on KafkaRebalance resource when an optimization proposal is ready * The ControlPlaneListener feature gate moves to GA * Add client rack-awareness support to Strimzi Bridge pods * Add support for OpenTelemetry for distributed tracing * ZookeeperRoller considers unready pods * Support multiple operations per ACLRule * Add new listener type "cluster-ip" which is using per-broker services instead of the pod DNS names For more details, all changes and installation files, go to https://github.com/strimzi/strimzi-kafka-operator/releases/tag/0.32.0-rc1 Any feedback can be provided on the Strimzi mailing list, on the #strimzi Slack channel on CNCF Slack or as a GitHub issue or discussion. Thanks & Regards Strimzi team |
|
|
|
[ANNOUNCE] [RELEASE] Strimzi Kafka Bridge 0.22.3
Paolo Patierno
New version 0.22.3 of Strimzi Kafka Bridge has been released. The main changes in this release are:
* 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)
* [CVE-2022-42003](https://nvd.nist.gov/vuln/detail/CVE-2022-42003)
* [CVE-2022-42004](https://nvd.nist.gov/vuln/detail/CVE-2022-42004)
For more details, go to https://github.com/strimzi/strimzi-kafka-bridge/releases/tag/0.22.3
Thanks to everyone who contributed to this release!
Strimzi team
Paolo Patierno
Senior Principal Software Engineer @ Red Hat
Microsoft MVP on Azure |
|
|