|
[ANNOUNCE] [RELEASE] Strimzi Kafka Operators 0.35.1
Jakub Scholz
Strimzi Kafka Operators 0.35.1 has been released. This patch release updates the Fabric8 Kubernetes Client used by Strimzi to a new version 6.7.0. For more details about this release and installation files, go to https://github.com/strimzi/strimzi-kafka-operator/releases/tag/0.35.1 Thanks to everyone who contributed to this release! Thanks & Regards Strimzi team |
|
|
|
RC1 of Strimzi Kafka Operators 0.35.1
Jakub Scholz
We prepared Release Candidate 1 of Strimzi Kafka Operators 0.35.1. The main change is an update to the Fabric8 Kubernetes Client. For more details, please visit the GitHub release page: https://github.com/strimzi/strimzi-kafka-operator/releases/tag/0.35.1-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 Operators 0.35.0
Jakub Scholz
Strimzi Kafka Operators 0.35.
The main changes in this release include: * Move feature gate UseStrimziPodSets to GA and remove support for StatefulSets
* Remove support for JMX Trans * Redesigned the Cluster and User Operator configuration to make it more efficient and flexible * Allow multiple Image Pull Secrets in the Strimzi Helm chart * Add flag to load Grafana dashboards from Helm Chart For more details about this release and installation files, go to https://github.com/strimzi/
You can also check a video about the main new features on our YouTube channel: https://youtu.be/oKr-
Thanks to everyone who contributed to this release!
Thanks & Regards
Strimzi team
|
|
|
|
How to start connector and to use a different connector configuration
tomerikick@...
If i would like to preserve consumer offsets for the connector a Connector with "_"
for example register it as x-y-z as set is to use the old x-y_z connectoer topic config
apiVersion: kafka.strimzi.io/v1beta2
kind: KafkaConnector
metadata:
name: x-y_z
spec:
class: io.confluent.connect.jdbc.JdbcSinkConnector
ConnectorName: x-y-z
|
|
|
|
Re: How to preserve offset for a Connector with "_" in his metadata name
Jakub Scholz
I'm afraid the only option to use a connector with `_` in its name is to not use the KafkaConnector resources but use the REST API directly instead (this is configured on the Connect cluster level through the annotation -> so this would apply to all connectors on given Connect cluster).
Thanks & Regards Jakub |
|
|
|
How to preserve offset for a Connector with "_" in his metadata name
tomerikick@...
How to preserve offset for a Connector with "_" in his metadata name
kind: KafkaConnector metadata: name: x-y_z I got a message: a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*') |
|
|
|
Re: How to move to KafkaConnect CRD with out deleting old KafkaConncetors
Jakub Scholz
Looks like the response did not make it to the list ... so resending again ...
When setting strimzi.io/use- There is currently no tool to do this for you - but maybe having something to prepare the KafkaConnector YAMLs for you would not be a bad idea. Feel free to open an enhancement issue for it on our GitHub if you want.
Thanks & Regards Jakub |
|
|
|
RC1 of Strimzi Kafka Operators 0.35.0 is available for testing
Jakub Scholz
Release candidate 1 of Strimzi Kafka Operators 0.
* Move feature gate UseStrimziPodSets to GA and remove support for StatefulSets
* Remove support for JMX Trans * Redesigned the Cluster and User Operator configuration to make it more efficient and flexible * Allow multiple Image Pull Secrets in the Strimzi Helm chart * Add flag to load Grafana dashboards from Helm Chart For more details, a full list of changes, and installation files, go to https://github.com/strimzi/
As usual, any feedback can be provided on the Strimzi mailing list, on the #strimzi channel on CNCF Slack, or as a GitHub issue or discussion.
Thanks & Regards
Strimzi team
|
|
|
|
How to move to KafkaConnect CRD with out deleting old KafkaConncetors
tomerikick@...
I have connectors which were set up using the API and not CRD of strimzi.io
Once i am setting strimzi.io/use-connector-resources: "true" in the KafkaConnect CRD
It will delete all KafkaConncetors
How to avoid this issue? How to move to KafkaConnect CRD with out deleting old KafkaConncetors? |
|
|
|
[PROPOSAL] Kafka Node Pools
Jakub Scholz
I opened a new Strimzi proposal which is about Kafka Node Pools => node pools provide a mechanism on how to run different sets of Kafka nodes with different configurations. It has quite a significant impact on how the custom resources will look and work. It should also provide new features - such as scaling-down brokers with any broker ID or better KRaft support. An aso provide basis for future improvements such as for example better autoscaling. If you are interested, feel free to check the proposal and comment on it here or on the PR. You can also check some demo videos of my prototype to better understand how would it look like in practice: * With ZooKeeper: https://youtu.be/KznxXsQNlq8 * In KRaft mode: https://youtu.be/_yx-0IWNsHc Thanks & Regards Jakub |
|
|
|
only one zookeeper pod is getting created
madhankannan7@...
Hi Team,
I am trying to created kafka cluster using strimzi , when i give replicas 3 for zookeeper the pods go to crashloop and when i give replicas 1 it runs perfectly . can you please help me fix this |
|
|
|
Re: Need some guidance with deploying NLB
Jakub Scholz
I do not think we have any documentation for this. Only this old blog post: https://strimzi.io/blog/2020/01/02/using-strimzi-with-amazon-nlb-loadbalancers/ What you are asking for is hard to use because Kubernetes provisions a new load balancer for each type=LoadBalancer service you create. So if you want to share one NLB, you have to do a lot of your own manual setup. Thanks & Regards Jakub On Tue, Apr 4, 2023 at 10:23 AM <madhankannan7@...> wrote:
|
|
|
|
Need some guidance with deploying NLB
madhankannan7@...
Dear Strimzi Support Team,
I am writing to request your assistance in configuring my Strimzi installation. I have been trying to set up my Apache Kafka cluster using Strimzi.
Specifically, I am facing issues with creating a single NLB that connects to kafka broker nodeport service and bootstrap nodeport service. I have followed the documentation available on your website, but I am still experiencing problems.
I would appreciate it if you could provide me with some guidance and support to help me overcome these issues. Please let me know if there are any additional details that you require from me in order to assist me better.
Thank you for your time and attention to my request. I look forward to hearing back from you soon. With Regards, |
|
|
|
[ANNOUNCE] [RELEASE] Strimzi Kubernetes Configuration Provider 1.1.1
Jakub Scholz
Kubernetes Configuration Provider 1.1.1 is now available: https://github.com/strimzi/kafka-kubernetes-config-provider/releases/tag/1.1.1 The main changes are: * Updated Kafka and Fabric8 dependencies to address CVEs * Use JDK HTTP Client instead of OkHttp Thanks to everyone who contributed to this release. Thanks & Regards Strimzi team |
|
|
|
RC1 of Kubernetes Configuration Provider 1.1.1
Jakub Scholz
Release Candidate 1 of Kubernetes Configuration Provider 1.1.1 is now available: https://github.com/strimzi/kafka-kubernetes-config-provider/releases/tag/1.1.1-rc1 The main changes are: * Updated Kafka and Fabric8 dependencies to address CVEs * Use JDK HTTP Client instead of OkHttp Any feedback can be provided on the Strimzi mailing list, on the #strimzi Slack channel on CNCF Slack, or as a GitHub discussion / issue. Thanks & Regards Strimzi team |
|
|
|
[ANNOUNCE] [RELEASE] Strimzi Kafka Operators 0.34.0
Jakub Scholz
Strimzi Kafka Operators 0.34.0 has been released. The main changes in this release include: * Support for Kafka 3.4.0 and removed support for Kafka 3.2.x * Stable Pod identities for Kafka Connect and MirrorMaker 2 * Use JDK HTTP client in the Kubernetes client instead of the OkHttp client * Add TLS truststore configuration for HTTPS connections to OPA server * Add image digest support in Helm chart * Update Strimzi HTTP Bridge to 0.25.0 and strimzi Oauth to 0.12.0 For more details about this release and installation files, go to https://github.com/strimzi/strimzi-kafka-operator/releases/tag/0.34.0 You can also check a video about the main new features on our YouTube channel: https://youtu.be/DtOTzBv-foI. Thanks to everyone who contributed to this release! Thanks & Regards Strimzi team |
|
|
|
RC1 of Strimzi Kafka Operators 0.34.0 is available for testing
Jakub Scholz
Release candidate 1 of Strimzi Kafka Operators 0.34.0 is now available for testing. The main improvements in this release include: * Add support for Kafka 3.4.0 and remove support for Kafka 3.2.x * Stable Pod identities for Kafka Connect and MirrorMaker 2 * Use JDK HTTP client in the Kubernetes client instead of the OkHttp client * Add TLS truststore configuration for HTTPS connections to OPA server * Add image digest support in Helm chart * Update Strimzi HTTP Bridge to 0.25.0 and strimzi Oauth to 0.12.0 For more details, a full list of changes, and installation files, go to https://github.com/strimzi/strimzi-kafka-operator/releases/tag/0.34.0-rc1 As usual, any feedback can be provided on the Strimzi mailing list, on the #strimzi channel on CNCF Slack, or as a GitHub issue or discussion. Thanks & Regards Strimzi team |
|
|
|
Re: Question regarding strimzi upgrade
Jakub Scholz
Hi Dmytro, Unfortunately, as you noted, Strimzi 0.13 does not support Kubernetes 1.22 because Strimzi 0.13 was written based on the apiextensions v1beta1 API. But Kube 1.22 and newer supports only apiextensions v1 API. The old APIs used by the older Stirmzi versions are not compatible with the new versions because Kubernetes changed what is allowed in the CRDs schemas. The proper upgrade path indeed was to upgrade to Strimzi 0.22, do the CRD conversion, then upgrade to Strimzi 0.23 (or newer), and only then upgrade to Kubernetes 1.22 (or newer). But the CRD conversion will not work for you if you are already on Kubernetes 1.22 and are using some modified CRDs (since the original would not work there). To be honest, there is no guide for how to deal with this situation as it was supposed to be upgraded way earlier and there is no tested approach. There were several Slack and GitHub discussion where you can check for the possible solutions. f I remember correctly, one of them was to delete the operator and do "non-cascading" deletion of the CRs & CRDs, install a new version of the operator and the new CRDs and create a new CRs to match the old ones but using the new versions to get the new operator to take over the old cluster. Another I think was to create your own CRDs with the new API versions without a schemas, upgrade Strimzi operator with it and only then install the actual new Strimzi CRDs. But you should definitely test them first in some test cluster. Another option is of course to downgrade the Kubernetes cluster, install the original old CRDs and follow the proper and tested upgrade procedure with the CRD conversion. Thanks & Regards Jakub On Wed, Mar 15, 2023 at 12:39 AM Dmytro Kondratskyi <kondratskyidmytro@...> wrote:
|
|
|
|
Question regarding strimzi upgrade
Dmytro Kondratskyi
Hello, I don't sure this is the right place to ask, I hope it is. I need
help with strimzi upgrade. The situation is: there is a strimzi 0.13.0 (and kafka 2.3.0)
installed in a kubernetes cluster, which was recently upgraded
from 1.15.3 to 1.22.8. Is it possible to properly upgrade strimzi and kafka to the
latest supported versions in this situation from 0.13.0 to 0.32.0
(kafka from 2.3.0 to 3.*)? The most important thing is to not
disrupt kafka data. I read that firstly strimzi should be upgraded to 0.22.0. But couldn't do it, because CRDs from this version use old kubernetes api v1beta1, and it is not supported in 1.22.8 now. If this is not the right place, please could you advice where I could get advice with this problem. |
|
|
|
[ANNOUNCE] [RELEASE] Strimzi Kafka Bridge 0.25.0
Paolo Patierno
New version 0.25.0 of Strimzi Kafka Bridge has been released.
### 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.
For more details, go to https://github.com/strimzi/strimzi-kafka-bridge/releases/tag/0.25.0
Thanks to everyone who contributed to this release!
Strimzi team
Paolo Patierno
Senior Principal Software Engineer @ Red Hat
Microsoft MVP on Azure |
|
|