[ANNOUNCE] [RELEASE] Strimzi Kafka Operators 0.20.0 released
Jakub Scholz
Strimzi Operators 0.20.0 is now available with a lot of important changes and improvements. The main changes since the 0.19.0 release include: * Add support for Kafka 2.5.1 and 2.6.0. Remove support for 2.4.0 and 2.4.1 * Make `listeners` configurable as an array and add support for more different listeners in single cluster * Remove TLS sidecars from Kafka pods => Kafka now uses native TLS to connect to ZooKeeper * Updated to Cruise Control 2.5.11, which adds Kafka 2.6.0 support and fixes a previous issue with CPU utilization statistics for containers. As a result, the CPUCapacityGoal has now been enabled. * Configure Cluster Operator logging using ConfigMap instead of environment variable and support dynamic changes * Switch to use the `AclAuthorizer` class for the `simple` Kafka authorization type. `AclAuthorizer` contains new features such as the ability to control the amount of authorization logs in the broker logs. * Support dynamic logging configuration of Kafka, Kafka Connect, Kafka Connect S2I and Kafka MirrorMaker2 * Add support for `client.rack` property for Kafka Connect to use `fetch from closest replica` feature. * Add support for configuring `hostAliases` in Pod templates * Cruise Control metrics integration including a new Grafana dashboard * Improved operators Grafana dashboard * Improvements to OAuth authentication and Keycloak authorization There are also some deprecations and removals which you should be aware of: * Deprecation of the old listener configuration * Removal of monitoring port on Kafka and ZooKeeper related services * Deprecation of Kafka TLS sidecar configuration 0.20.0 will also be the last version of Strimzi that will support Kubernetes 1.11-1.15. Future versions will support Kubernetes 1.16+. For more details and installation files, go to https://github.com/strimzi/strimzi-kafka-operator/releases/tag/0.20.0 Many thanks to everyone who contributed to this release! Thanks & Regards Strimzi team
|
|
RC3 of Strimzi Operators 0.20.0
Jakub Scholz
Release Candidate 3 of Strimzi Operators 0.20.0 is now available for testing. Compared to the Release Candidate 2, there are several bugfixes and improvements: * Fix rolling updates when all Kafka pods are Pending (#3848) * Bump OPA Authorizer version to fix CVE in its dependencies (#3853) * Fix rebalance examples (#3838) * Fix cAdvisor metric labels (#3840) * Several docs and system test fixes and improvements Note: 0.20.0 will be the last version of Strimzi that will support Kubernetes 1.11-1.15. Future versions will support Kubernetes 1.16+. For more details and installation files, go to https://github.com/strimzi/strimzi-kafka-operator/releases/tag/0.20.0-rc3 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 Jakub
|
|
RC2 of Strimzi Operators 0.20.0
Jakub Scholz
Release Candidate 2 of Strimzi Operators 0.20.0 is now available for testing. Compared to the Release Candidate 1, there are several bugfixes and improvements: * Fix secrets with `.` in name (#3820) * Fix leak of HTTPClients in Connector Operator (#3827) * Fix handling of custom and OAuth certificates (#3825) * Upgrade JMX Exporter to 0.14.0 * Several docs and system test fixes and improvements Note: 0.20.0 will be the last version of Strimzi that will support Kubernetes 1.11-1.15. Future versions will support Kubernetes 1.16+. For more details and installation files, go to https://github.com/strimzi/strimzi-kafka-operator/releases/tag/0.20.0-rc2 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 Jakub
|
|
RC1 of Strimzi Operators 0.20.0
Jakub Scholz
Hi, Release Candidate 1 of Strimzi Operators 0.20.0 is now available for testing with a lot of changes and improvements. The main changes since the 0.19.0 release include: * Add support for Kafka 2.5.1 and 2.6.0. Remove support for 2.4.0 and 2.4.1 * Make `listeners` configurable as an array and add support for more different listeners in single cluster * Remove TLS sidecars from Kafka pods => Kafka now uses native TLS to connect to ZooKeeper * Updated to Cruise Control 2.5.11, which adds Kafka 2.6.0 support and fixes a previous issue with CPU utilization statistics for containers. As a result, the CPUCapacityGoal has now been enabled. * Configure Cluster Operator logging using ConfigMap instead of environment variable and support dynamic changes * Switch to use the `AclAuthorizer` class for the `simple` Kafka authorization type. `AclAuthorizer` contains new features such as the ability to control the amount of authorization logs in the broker logs. * Support dynamic logging configuration of Kafka, Kafka Connect, Kafka Connect S2I and Kafka MirrorMaker2 * Add support for `client.rack` property for Kafka Connect to use `fetch from closest replica` feature. * Add support for configuring `hostAliases` in Pod templates * Cruise Control metrics integration including a new Grafana dashboard * Improved operators Grafana dashboard There are also some deprecations and removals which you should be aware of: * Deprecation of the old listener configuration * Removal of monitoring port on Kafka and ZooKeeper related services * Deprecation of Kafka TLS sidecar configuration 0.20.0 will also be the last version of Strimzi that will support Kubernetes 1.11-1.15. Future versions will support Kubernetes 1.16+. For more details and installation files, go to https://github.com/strimzi/strimzi-kafka-operator/releases/tag/0.20.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 Jakub
|
|
[ANNOUNCE] Strimzi Kafka Bridge 0.19.0 released!
Paolo Patierno
Version 0.19.0 of Strimzi Kafka Bridge has been released.
The main changes include:
For more details, go to https://github.com/strimzi/strimzi-kafka-bridge/releases/tag/0.19.0
Thanks,
Paolo
Paolo Patierno
Principal Software Engineer @ Red Hat
Microsoft MVP on Azure
|
|
Re: RC1 of Strimzi Kafka Bridge 0.19.0
Jakub Scholz
+1 (binding) ... I run my tests with the bridge RC1 used used Strimzi operators ad did not found any issues, all seemed to work fine. Jakub
On Wed, Sep 30, 2020 at 4:22 PM Paolo Patierno <ppatierno@...> wrote:
|
|
RC1 of Strimzi Kafka Bridge 0.19.0
Paolo Patierno
Hi all,
Release Candidate 1 of Strimzi Kafka Bridge 0.19.0 is now available for testing.
The main changes since 0.18.0 include:
For more details and binaries, go to
https://github.com/strimzi/strimzi-kafka-bridge/releases/tag/0.19.0-rc1
Any feedback can be provided here or as a GitHub issue.
Paolo Patierno
Principal Software Engineer @ Red Hat
Microsoft MVP on Azure
|
|
[ANNOUNCE] [RELEASE] Strimzi Kafka OAuth library 0.6.1 released
Jakub Scholz
Version 0.6.1 of the Strimzi Kafka OAuth library is now available: https://github.com/strimzi/strimzi-kafka-oauth/releases/tag/0.6.1. The release contains an updated version of the Keycloak dependency. Thanks & Regards Jakub
|
|
Re: Kafka broker pods are not coming up and unable to create statefulset
Jakub Scholz
I guess it might depend on your MetalLB configuration. I use it on my local Kube cluster without any special settings. But in your case, it looks like the LoadBalancers are not being provisioned. You can use `kubectl get service` to see if at least some were provisioned or not. In case you want the LoadBalancers with some specific IP address, you can also use this in the KAfka CR: external: type: loadbalancer tls: false overrides: bootstrap: loadBalancerIP: 172.29.3.10 brokers: - broker: 0 loadBalancerIP: 172.29.3.1 - broker: 1 loadBalancerIP: 172.29.3.2 - broker: 2 loadBalancerIP: 172.29.3.3 This should make sure that the loadbalancers get these assigned IP addresses if possible. But as I said - not needed on my MetalLB installation. But you can give it a try. If you want to use an annotation on the service (such as metallb.universe.tf/allow-shared-ip), you can use the perPodService and exteralBootstrapService options here: https://strimzi.io/docs/operators/latest/full/using.html#type-KafkaClusterTemplate-reference ... but I don't think Kafka will work with a shared IP address. Thanks & Regards Jakub
On Fri, Sep 18, 2020 at 5:09 PM <tsnagraj.08@...> wrote:
|
|
Kafka broker pods are not coming up and unable to create statefulset
Nag Raj
Hi Team, apiVersion: kafka.strimzi.io/v1beta1 kind: Kafka metadata: name: my-cluster annotations: metallb.universe.tf/allow-shared-ip: smart spec: loadBalancerIP: xxxxxxx kafka: version: 2.5.0 replicas: 3 listeners: plain: {} tls: {} external: type: loadbalancer tls: false config: offsets.topic.replication.factor: 3 transaction.state.log.replication.factor: 3 transaction.state.log.min.isr: 2 log.message.format.version: "2.5" storage: type: persistent-claim size: 10Gi class: sc-paas deleteClaim: false resources: requests: memory: 8Gi cpu: "1" limits: memory: 24Gi cpu: "3" zookeeper: replicas: 3 resources: requests: memory: 8Gi cpu: "1" limits: memory: 24Gi cpu: "3" storage: type: persistent-claim size: 10Gi class: sc-paas deleteClaim: false entityOperator: topicOperator: {} userOperator: {} 2020-09-18 13:08:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 13:10:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 13:12:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 13:14:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 13:16:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 13:18:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 13:20:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 13:22:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 13:23:40 INFO OperatorWatcher:40 - Reconciliation #11(watch) Kafka(kafka-op-test/my-cluster): Kafka my-cluster in namespace kafka-op-test was ADDED 2020-09-18 13:23:40 INFO AbstractOperator:173 - Reconciliation #11(watch) Kafka(kafka-op-test/my-cluster): Kafka my-cluster should be created or updated 2020-09-18 13:23:40 INFO OperatorWatcher:40 - Reconciliation #12(watch) Kafka(kafka-op-test/my-cluster): Kafka my-cluster in namespace kafka-op-test was MODIFIED 2020-09-18 13:23:50 WARN AbstractOperator:247 - Reconciliation #12(watch) Kafka(kafka-op-test/my-cluster): Failed to acquire lock lock::kafka-op-test::Kafka::my-cluster within 10000ms. 2020-09-18 13:24:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 13:24:29 WARN AbstractOperator:247 - Reconciliation #13(timer) Kafka(kafka-op-test/my-cluster): Failed to acquire lock lock::kafka-op-test::Kafka::my-cluster within 10000ms. 2020-09-18 13:26:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 13:26:29 WARN AbstractOperator:247 - Reconciliation #14(timer) Kafka(kafka-op-test/my-cluster): Failed to acquire lock lock::kafka-op-test::Kafka::my-cluster within 10000ms. 2020-09-18 13:28:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 13:28:29 WARN AbstractOperator:247 - Reconciliation #15(timer) Kafka(kafka-op-test/my-cluster): Failed to acquire lock lock::kafka-op-test::Kafka::my-cluster within 10000ms. 2020-09-18 13:29:52 ERROR Util:120 - Exceeded timeout of 300000ms while waiting for Service resource my-cluster-kafka-external-bootstrap in namespace kafka-op-test to be addressable 2020-09-18 13:29:52 WARN KafkaAssemblyOperator:1866 - Reconciliation #11(watch) Kafka(kafka-op-test/my-cluster): No loadbalancer address found in the Status section of Service my-cluster-kafka-external-bootstrap resource. Loadbalancer was probably not provisioned. 2020-09-18 13:29:52 INFO OperatorWatcher:40 - Reconciliation #16(watch) Kafka(kafka-op-test/my-cluster): Kafka my-cluster in namespace kafka-op-test was MODIFIED 2020-09-18 13:29:52 ERROR AbstractOperator:175 - Reconciliation #11(watch) Kafka(kafka-op-test/my-cluster): createOrUpdate failed io.vertx.core.impl.NoStackTraceThrowable: No loadbalancer address found in the Status section of Service my-cluster-kafka-external-bootstrap resource. Loadbalancer was probably not provisioned. 2020-09-18 13:29:52 WARN AbstractOperator:330 - Reconciliation #11(watch) Kafka(kafka-op-test/my-cluster): Failed to reconcile io.vertx.core.impl.NoStackTraceThrowable: No loadbalancer address found in the Status section of Service my-cluster-kafka-external-bootstrap resource. Loadbalancer was probably not provisioned. 2020-09-18 13:29:52 INFO AbstractOperator:173 - Reconciliation #16(watch) Kafka(kafka-op-test/my-cluster): Kafka my-cluster should be created or updated 2020-09-18 13:30:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 13:30:29 WARN AbstractOperator:247 - Reconciliation #17(timer) Kafka(kafka-op-test/my-cluster): Failed to acquire lock lock::kafka-op-test::Kafka::my-cluster within 10000ms. 2020-09-18 13:32:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 13:32:29 WARN AbstractOperator:247 - Reconciliation #18(timer) Kafka(kafka-op-test/my-cluster): Failed to acquire lock lock::kafka-op-test::Kafka::my-cluster within 10000ms. 2020-09-18 13:33:46 INFO OperatorWatcher:40 - Reconciliation #19(watch) Kafka(kafka-op-test/my-cluster): Kafka my-cluster in namespace kafka-op-test was MODIFIED 2020-09-18 13:33:56 WARN AbstractOperator:247 - Reconciliation #19(watch) Kafka(kafka-op-test/my-cluster): Failed to acquire lock lock::kafka-op-test::Kafka::my-cluster within 10000ms. 2020-09-18 13:34:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 13:34:29 WARN AbstractOperator:247 - Reconciliation #20(timer) Kafka(kafka-op-test/my-cluster): Failed to acquire lock lock::kafka-op-test::Kafka::my-cluster within 10000ms. 2020-09-18 13:34:44 INFO OperatorWatcher:40 - Reconciliation #21(watch) Kafka(kafka-op-test/my-cluster): Kafka my-cluster in namespace kafka-op-test was DELETED 2020-09-18 13:34:53 ERROR Util:120 - Exceeded timeout of 300000ms while waiting for Service resource my-cluster-kafka-external-bootstrap in namespace kafka-op-test to be addressable 2020-09-18 13:34:53 WARN KafkaAssemblyOperator:1866 - Reconciliation #16(watch) Kafka(kafka-op-test/my-cluster): No loadbalancer address found in the Status section of Service my-cluster-kafka-external-bootstrap resource. Loadbalancer was probably not provisioned. 2020-09-18 13:34:53 ERROR KafkaAssemblyOperator:498 - Reconciliation #16(watch) Kafka(kafka-op-test/my-cluster): Current Kafka resource not found 2020-09-18 13:34:53 ERROR KafkaAssemblyOperator:244 - Failed to set status for my-cluster 2020-09-18 13:34:53 ERROR AbstractOperator:175 - Reconciliation #16(watch) Kafka(kafka-op-test/my-cluster): createOrUpdate failed io.vertx.core.impl.NoStackTraceThrowable: No loadbalancer address found in the Status section of Service my-cluster-kafka-external-bootstrap resource. Loadbalancer was probably not provisioned. 2020-09-18 13:34:53 WARN AbstractOperator:330 - Reconciliation #16(watch) Kafka(kafka-op-test/my-cluster): Failed to reconcile io.vertx.core.impl.NoStackTraceThrowable: No loadbalancer address found in the Status section of Service my-cluster-kafka-external-bootstrap resource. Loadbalancer was probably not provisioned. 2020-09-18 13:34:53 INFO AbstractOperator:179 - Reconciliation #21(watch) Kafka(kafka-op-test/my-cluster): Kafka my-cluster should be deleted 2020-09-18 13:34:53 INFO AbstractOperator:184 - Reconciliation #21(watch) Kafka(kafka-op-test/my-cluster): Assembly my-cluster should be deleted by garbage collection 2020-09-18 13:34:53 INFO AbstractOperator:318 - Reconciliation #21(watch) Kafka(kafka-op-test/my-cluster): reconciled 2020-09-18 13:35:36 INFO OperatorWatcher:40 - Reconciliation #22(watch) Kafka(kafka-op-test/my-cluster): Kafka my-cluster in namespace kafka-op-test was ADDED 2020-09-18 13:35:36 WARN AbstractOperator:106 - Kafka resource my-cluster in namespace kafka-op-test: Contains object at path spec with an unknown property: loadBalancerIP 2020-09-18 13:35:36 INFO AbstractOperator:173 - Reconciliation #22(watch) Kafka(kafka-op-test/my-cluster): Kafka my-cluster should be created or updated 2020-09-18 13:35:36 INFO OperatorWatcher:40 - Reconciliation #23(watch) Kafka(kafka-op-test/my-cluster): Kafka my-cluster in namespace kafka-op-test was MODIFIED 2020-09-18 13:35:46 WARN AbstractOperator:247 - Reconciliation #23(watch) Kafka(kafka-op-test/my-cluster): Failed to acquire lock lock::kafka-op-test::Kafka::my-cluster within 10000ms. 2020-09-18 13:36:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 13:36:29 WARN AbstractOperator:247 - Reconciliation #24(timer) Kafka(kafka-op-test/my-cluster): Failed to acquire lock lock::kafka-op-test::Kafka::my-cluster within 10000ms. 2020-09-18 13:38:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 13:38:29 WARN AbstractOperator:247 - Reconciliation #25(timer) Kafka(kafka-op-test/my-cluster): Failed to acquire lock lock::kafka-op-test::Kafka::my-cluster within 10000ms. 2020-09-18 13:40:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 13:40:29 WARN AbstractOperator:247 - Reconciliation #26(timer) Kafka(kafka-op-test/my-cluster): Failed to acquire lock lock::kafka-op-test::Kafka::my-cluster within 10000ms. 2020-09-18 13:41:22 ERROR Util:120 - Exceeded timeout of 300000ms while waiting for Service resource my-cluster-kafka-external-bootstrap in namespace kafka-op-test to be addressable 2020-09-18 13:41:22 WARN KafkaAssemblyOperator:1866 - Reconciliation #22(watch) Kafka(kafka-op-test/my-cluster): No loadbalancer address found in the Status section of Service my-cluster-kafka-external-bootstrap resource. Loadbalancer was probably not provisioned. 2020-09-18 13:41:22 ERROR AbstractOperator:175 - Reconciliation #22(watch) Kafka(kafka-op-test/my-cluster): createOrUpdate failed io.vertx.core.impl.NoStackTraceThrowable: No loadbalancer address found in the Status section of Service my-cluster-kafka-external-bootstrap resource. Loadbalancer was probably not provisioned. 2020-09-18 13:41:22 INFO OperatorWatcher:40 - Reconciliation #27(watch) Kafka(kafka-op-test/my-cluster): Kafka my-cluster in namespace kafka-op-test was MODIFIED 2020-09-18 13:41:22 WARN AbstractOperator:330 - Reconciliation #22(watch) Kafka(kafka-op-test/my-cluster): Failed to reconcile io.vertx.core.impl.NoStackTraceThrowable: No loadbalancer address found in the Status section of Service my-cluster-kafka-external-bootstrap resource. Loadbalancer was probably not provisioned. 2020-09-18 13:41:22 WARN AbstractOperator:106 - Kafka resource my-cluster in namespace kafka-op-test: Contains object at path spec with an unknown property: loadBalancerIP 2020-09-18 13:41:22 INFO AbstractOperator:173 - Reconciliation #27(watch) Kafka(kafka-op-test/my-cluster): Kafka my-cluster should be created or updated 2020-09-18 13:42:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 13:42:29 WARN AbstractOperator:247 - Reconciliation #28(timer) Kafka(kafka-op-test/my-cluster): Failed to acquire lock lock::kafka-op-test::Kafka::my-cluster within 10000ms. 2020-09-18 13:44:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 13:44:29 WARN AbstractOperator:247 - Reconciliation #29(timer) Kafka(kafka-op-test/my-cluster): Failed to acquire lock lock::kafka-op-test::Kafka::my-cluster within 10000ms. 2020-09-18 13:46:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 13:46:23 ERROR Util:120 - Exceeded timeout of 300000ms while waiting for Service resource my-cluster-kafka-external-bootstrap in namespace kafka-op-test to be addressable 2020-09-18 13:46:23 WARN KafkaAssemblyOperator:1866 - Reconciliation #27(watch) Kafka(kafka-op-test/my-cluster): No loadbalancer address found in the Status section of Service my-cluster-kafka-external-bootstrap resource. Loadbalancer was probably not provisioned. 2020-09-18 13:46:23 ERROR AbstractOperator:175 - Reconciliation #27(watch) Kafka(kafka-op-test/my-cluster): createOrUpdate failed io.vertx.core.impl.NoStackTraceThrowable: No loadbalancer address found in the Status section of Service my-cluster-kafka-external-bootstrap resource. Loadbalancer was probably not provisioned. 2020-09-18 13:46:23 WARN AbstractOperator:330 - Reconciliation #27(watch) Kafka(kafka-op-test/my-cluster): Failed to reconcile io.vertx.core.impl.NoStackTraceThrowable: No loadbalancer address found in the Status section of Service my-cluster-kafka-external-bootstrap resource. Loadbalancer was probably not provisioned. 2020-09-18 13:46:23 WARN AbstractOperator:106 - Kafka resource my-cluster in namespace kafka-op-test: Contains object at path spec with an unknown property: loadBalancerIP 2020-09-18 13:46:23 INFO AbstractOperator:173 - Reconciliation #30(timer) Kafka(kafka-op-test/my-cluster): Kafka my-cluster should be created or updated 2020-09-18 13:48:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 13:48:29 WARN AbstractOperator:247 - Reconciliation #31(timer) Kafka(kafka-op-test/my-cluster): Failed to acquire lock lock::kafka-op-test::Kafka::my-cluster within 10000ms. 2020-09-18 13:50:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 13:50:29 WARN AbstractOperator:247 - Reconciliation #32(timer) Kafka(kafka-op-test/my-cluster): Failed to acquire lock lock::kafka-op-test::Kafka::my-cluster within 10000ms. 2020-09-18 13:51:25 ERROR Util:120 - Exceeded timeout of 300000ms while waiting for Service resource my-cluster-kafka-external-bootstrap in namespace kafka-op-test to be addressable 2020-09-18 13:51:25 WARN KafkaAssemblyOperator:1866 - Reconciliation #30(timer) Kafka(kafka-op-test/my-cluster): No loadbalancer address found in the Status section of Service my-cluster-kafka-external-bootstrap resource. Loadbalancer was probably not provisioned. 2020-09-18 13:51:25 ERROR AbstractOperator:175 - Reconciliation #30(timer) Kafka(kafka-op-test/my-cluster): createOrUpdate failed io.vertx.core.impl.NoStackTraceThrowable: No loadbalancer address found in the Status section of Service my-cluster-kafka-external-bootstrap resource. Loadbalancer was probably not provisioned. 2020-09-18 13:51:25 WARN AbstractOperator:330 - Reconciliation #30(timer) Kafka(kafka-op-test/my-cluster): Failed to reconcile io.vertx.core.impl.NoStackTraceThrowable: No loadbalancer address found in the Status section of Service my-cluster-kafka-external-bootstrap resource. Loadbalancer was probably not provisioned. 2020-09-18 13:52:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 13:52:19 WARN AbstractOperator:106 - Kafka resource my-cluster in namespace kafka-op-test: Contains object at path spec with an unknown property: loadBalancerIP 2020-09-18 13:52:19 INFO AbstractOperator:173 - Reconciliation #33(timer) Kafka(kafka-op-test/my-cluster): Kafka my-cluster should be created or updated 2020-09-18 13:54:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 13:54:29 WARN AbstractOperator:247 - Reconciliation #34(timer) Kafka(kafka-op-test/my-cluster): Failed to acquire lock lock::kafka-op-test::Kafka::my-cluster within 10000ms. 2020-09-18 13:56:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 13:56:29 WARN AbstractOperator:247 - Reconciliation #35(timer) Kafka(kafka-op-test/my-cluster): Failed to acquire lock lock::kafka-op-test::Kafka::my-cluster within 10000ms. 2020-09-18 13:57:20 ERROR Util:120 - Exceeded timeout of 300000ms while waiting for Service resource my-cluster-kafka-external-bootstrap in namespace kafka-op-test to be addressable 2020-09-18 13:57:20 WARN KafkaAssemblyOperator:1866 - Reconciliation #33(timer) Kafka(kafka-op-test/my-cluster): No loadbalancer address found in the Status section of Service my-cluster-kafka-external-bootstrap resource. Loadbalancer was probably not provisioned. 2020-09-18 13:57:20 ERROR AbstractOperator:175 - Reconciliation #33(timer) Kafka(kafka-op-test/my-cluster): createOrUpdate failed io.vertx.core.impl.NoStackTraceThrowable: No loadbalancer address found in the Status section of Service my-cluster-kafka-external-bootstrap resource. Loadbalancer was probably not provisioned. 2020-09-18 13:57:20 WARN AbstractOperator:330 - Reconciliation #33(timer) Kafka(kafka-op-test/my-cluster): Failed to reconcile io.vertx.core.impl.NoStackTraceThrowable: No loadbalancer address found in the Status section of Service my-cluster-kafka-external-bootstrap resource. Loadbalancer was probably not provisioned. 2020-09-18 13:58:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 13:58:19 WARN AbstractOperator:106 - Kafka resource my-cluster in namespace kafka-op-test: Contains object at path spec with an unknown property: loadBalancerIP 2020-09-18 13:58:19 INFO AbstractOperator:173 - Reconciliation #36(timer) Kafka(kafka-op-test/my-cluster): Kafka my-cluster should be created or updated 2020-09-18 14:00:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 14:00:29 WARN AbstractOperator:247 - Reconciliation #37(timer) Kafka(kafka-op-test/my-cluster): Failed to acquire lock lock::kafka-op-test::Kafka::my-cluster within 10000ms. 2020-09-18 14:02:19 INFO ClusterOperator:125 - Triggering periodic reconciliation for namespace kafka-op-test... 2020-09-18 14:02:29 WARN AbstractOperator:247 - Reconciliation #38(timer) Kafka(kafka-op-test/my-cluster): Failed to acquire lock lock::kafka-op-test::Kafka::my-cluster within 10000ms. 2020-09-18 14:03:20 ERROR Util:120 - Exceeded timeout of 300000ms while waiting for Service resource my-cluster-kafka-external-bootstrap in namespace kafka-op-test to be addressable 2020-09-18 14:03:20 WARN KafkaAssemblyOperator:1866 - Reconciliation #36(timer) Kafka(kafka-op-test/my-cluster): No loadbalancer address found in the Status section of Service my-cluster-kafka-external-bootstrap resource. Loadbalancer was probably not provisioned. 2020-09-18 14:03:20 ERROR AbstractOperator:175 - Reconciliation #36(timer) Kafka(kafka-op-test/my-cluster): createOrUpdate failed io.vertx.core.impl.NoStackTraceThrowable: No loadbalancer address found in the Status section of Service my-cluster-kafka-external-bootstrap resource. Loadbalancer was probably not provisioned. 2020-09-18 14:03:20 WARN AbstractOperator:330 - Reconciliation #36(timer) Kafka(kafka-op-test/my-cluster): Failed to reconcile io.vertx.core.impl.NoStackTraceThrowable: No loadbalancer address found in the Status section of Service my-cluster-kafka-external-bootstrap resource. Loadbalancer was probably not provisioned.
|
|
Re: Kafka Bridging Startup Error
Paolo Patierno
Hi,
which version of the bridge are you using? I have just downloaded and tried the latest 0.18.0 release (https://github.com/strimzi/strimzi-kafka-bridge/releases/tag/0.18.0) copy/pasting
the same command you are executing and it's working fine with me.
Thanks.
Paolo Patierno
Principal Software Engineer @ Red Hat
Microsoft MVP on Azure
From: cncf-strimzi-users@... <cncf-strimzi-users@...> on behalf of msjyosh@... <msjyosh@...>
Sent: Thursday, September 10, 2020 8:24 PM To: cncf-strimzi-users@... <cncf-strimzi-users@...> Subject: [cncf-strimzi-users] Kafka Bridging Startup Error Hi, When i am trying to start KafkaBridge script I am getting below error
bin/kafka_bridge_run.sh --config-file config/application.properties
Error: Could not find or load main class io.strimzi.kafka.bridge.Application
please advise on what could be the issue ? If i am missing anything !?
|
|
Kafka Bridging Startup Error
msjyosh@...
Hi, When i am trying to start KafkaBridge script I am getting below error
bin/kafka_bridge_run.sh --config-file config/application.properties
Error: Could not find or load main class io.strimzi.kafka.bridge.Application
please advise on what could be the issue ? If i am missing anything !?
|
|
Strimzi Kafka OAuth library 0.6.0 released
Jakub Scholz
Hi, Version 0.6.0 of the Strimzi Kafka OAuth library has been released! The main changes since last release are: * Optimized internals * Improved server-side logging * Improved handling of expired or otherwise invalidated access tokens ** Fixed, and documented the re-authentication support ** Added OAuthSessionAuthorizer ** Deprecated the JwtKafkaPrincipalBuilder in favor of the new OAuthKafkaPrincipalBuilder ** KeycloakRBACAuthorizer improvements ** Introduced fast JWKS keys refresh ** Fixed exception types thrown during token validation For more details go to the GitHub release page: https://github.com/strimzi/strimzi-kafka-oauth/releases/tag/0.6.0 Thanks a lot to everyone who contributed to this release by raising issues, opening PRs etc. And especially to Marko who did most of the work! Thanks & Regards Jakub
|
|
RC1 of Strimzi Kafka OAuth library 0.6.0
Jakub Scholz
Hi, Release Candidate 1 of the 0.6.0 version of the Strimzi Kafka OAuth library is now available for testing: https://github.com/strimzi/strimzi-kafka-oauth/releases/tag/0.6.0-rc1. The main changes are: * Optimized internals * Improved server-side logging * Improved handling of expired or otherwise invalidated access tokens ** Fixed, and documented the re-authentication support ** Added OAuthSessionAuthorizer ** Deprecated the JwtKafkaPrincipalBuilder in favor of the new OAuthKafkaPrincipalBuilder ** KeycloakRBACAuthorizer improvements ** Introduced fast JWKS keys refresh ** Fixed exception types thrown during token validation To test it, you can use the staging Maven repository: <repositories> <repository> <id>staging</id> <url>https://oss.sonatype.org/content/repositories/iostrimzi-1073</url> </repository> </repositories> Any feedback can be provided here, on Slack or as a GitHub issue. Thanks & Regards Jakub
|
|
The first Strimzi survey is here!
Paolo Patierno
Do you want to spend 5 minutes to help us improve Strimzi?
The first Strimzi survey is here! We would like to hear more from you, where and how you are using it.
Thanks,
Paolo
Paolo Patierno
Principal Software Engineer @ Red Hat
Microsoft MVP on Azure
|
|
Are you using Strimzi in production? Let us know about it!
Jakub Scholz
Are you using Strimzi in production? Let us know about it! Having an overview of Strimzi adopters is not important just for us in the Strimzi team. It also helps new users who decide whether to use Strimzi. And it is also part of the CNCF annual review and graduation process which is really important for the whole Strimzi community. Having the list of adopters up to date would help us with our annual review which will happen later this summer. We have two places for keeping track of production users: * The ADOPTERS.md file * The company logos in the _used by_ section on Strimzi website You can just open a PR to add your company to the ADOPTERS.md file or to the website. Or you can also get in touch with any of the Strimzi maintainers and we will help you with it. Thanks for your help. Jakub & Strimzi maintainers team
|
|
[ANNOUNCE] [RELEASE] Strimzi Kafka Operators 0.19.0 released
Jakub Scholz
Hi, Strimzi Kafka Operators 0.19.0 has been released with a lot of changes and improvements. The main changes since the 0.18.0 release include: * Add support for authorization using Open Policy Agent * Add support for scale subresource to make scaling of following resources easier: * KafkaConnect * KafkaConnectS2I * KafkaBridge * KafkaMirrorMaker * KafkaMirrorMaker2 * KafkaConnector * Remove deprecated `Kafka.spec.topicOperator` classes and deployment logic * Use Java 11 as the Java runtime * Removed the need to manually create Cruise Control metrics topics if topic auto creation is disabled. * Migration to Helm 3 * Refactored the format of the `KafkaRebalance` resource's status. The state of the rebalance is now displayed in the associated `Condition`'s `type` field rather than the `status` field. This was done so that the information would display correctly in various Kubernetes tools. * Added performance tuning options to the `KafkaRebalance` CR and the ability to define a regular expression that will exclude matching topics from a rebalance optimization proposal. * Use Strimzi Kafka Bridge 0.18.0 * Make it possible to configure labels and annotations for secrets created by the User Operator * Strimzi Kafka Bridge metrics integration: * Enable/disable metrics in the KafkaBridge custom resource * New Grafana dashboard for the bridge metrics * Support dynamically changeable logging in the Entity Operator and Kafka Bridge There are also some deprecations and removals which you should be aware of: * Deprecation of Helm v2 chart * Removal deprecated cadvisor metric labels * Deprecation of monitoring port on Kafka and ZooKeeper related services In the next version, we will also remove the support for the v1alpha1 resources deprecated in Strimzi 0.12.0. For more details and installation files, go to https://github.com/strimzi/strimzi-kafka-operator/releases/tag/0.19.0. Documentation and Quick Starts can be found on our website https://strimzi.io/. Thanks to everyone who contributed to this release! Thanks & Regards Jakub
|
|
RC1 of Strimzi Operators 0.19.0
Jakub Scholz
Hi, Release Candidate 1 of Strimzi Operators 0.19.0 is now available for testing with a lot of changes and improvements. The main changes since the 0.18.0 release include: * Add support for authorization using Open Policy Agent * Add support for scale subresource to make scaling of following resources easier: * KafkaConnect * KafkaConnectS2I * KafkaBridge * KafkaMirrorMaker * KafkaMirrorMaker2 * KafkaConnector * Remove deprecated `Kafka.spec.topicOperator` classes and deployment logic * Use Java 11 as the Java runtime * Removed the need to manually create Cruise Control metrics topics if topic auto creation is disabled. * Migration to Helm 3 * Refactored the format of the `KafkaRebalance` resource's status. The state of the rebalance is now displayed in the associated `Condition`'s `type` field rather than the `status` field. This was done so that the information would display correctly in various Kubernetes tools. * Added performance tuning options to the `KafkaRebalance` CR and the ability to define a regular expression that will exclude matching topics from a rebalance optimization proposal. * Use Strimzi Kafka Bridge 0.18.0 * Make it possible to configure labels and annotations for secrets created by the User Operator * Strimzi Kafka Bridge metrics integration: * Enable/disable metrics in the KafkaBridge custom resource * New Grafana dashboard for the bridge metrics * Support dynamically changeable logging in the Entity Operator and Kafka Bridge There are also some deprecations and removals which you should be aware of: * Deprecation of Helm v2 chart * Removal deprecated cadvisor metric labels * Deprecation of monitoring port on Kafka and ZooKeeper related services In the next version, we will also remove the support for the v1alpha1 resources deprecated in Strimzi 0.12.0. For more details and installation files, go to https://github.com/strimzi/strimzi-kafka-operator/releases/tag/0.19.0-rc1 Any feedback can be provided here, on the #strimzi Slack channel on CNCF Slack or as a GitHub issue. Thanks & Regards Jakub
|
|
Re: Is it possible to manager external cluster topics and users using Strimzi operator
Jakub Scholz
I already answered this on Slack ... but just for the archives. The Topic and User Operator can be used with any Kafka cluster. More details can be found in the docs: * https://strimzi.io/docs/operators/latest/deploying.html#deploying-the-topic-operator-standalone-str * https://strimzi.io/docs/operators/latest/deploying.html#deploying-the-user-operator-standalone-str Jakub
On Mon, Jul 13, 2020 at 9:07 PM <uday.jalagam@...> wrote: Hello ,
|
|
Is it possible to manager external cluster topics and users using Strimzi operator
uday.jalagam@...
Hello ,
Is it possible to manage existing kafka cluster outside kubernetes using Strimzi topic and user operator ? Just want to create topic based on CRD and same way for user if possible . Are those only depend on the service or any other dependencies to manage cluster ? Thanks, Uday.
|
|