From jakub at scholz.cz Mon Feb 4 19:24:33 2019 From: jakub at scholz.cz (Jakub Scholz) Date: Mon, 4 Feb 2019 20:24:33 +0100 Subject: [Strimzi] [Release] Strimzi 0.10.0 Message-ID: Strimzi 0.10.0 has been released. The main changes include: * Kafka 2.1.0 * Kafka upgrades * Secrets management for Kafka Connect * Network Policy management * and many more. For more details go to http://strimzi.io/ and/or https://github.com/strimzi/strimzi-kafka-operator/releases/tag/0.10.0 Thanks to everyone who contributed to this release. Thanks & Regards Jakub -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.Schwarz at prosoz.de Thu Feb 21 10:07:43 2019 From: M.Schwarz at prosoz.de (Schwarz, Markus) Date: Thu, 21 Feb 2019 10:07:43 +0000 Subject: [Strimzi] Configure logging for kafka brokers Message-ID: <7f379179f07d403c89cb6c85980ba157@prosoz.de> Hi, I?d like to have the kafka broker logs included in our log aggregation tooling (Filebeat, Elasticsearch, Kibana) . For that to work I need the broker logs to be written into a directory mounted as volume inside the broker container. Now I got two problems: - How can I tell the broker where to put its logfiles? As I understand the corresponding kafka configuration options are ?forbidden? in strimzi. - How can I tell the operator to add a volume mount to the broker pods? - Is there any other way to get the logs into elasticsearch? I?m using strimzi 0.9.0 at the moment, update to 0.10.0 will happen in the next 3-4 weeks. Thanks, Markus [cid:image464079.PNG at 53aba97c.43b78f40] prosoz-herten-footer -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image464079.PNG Type: image/png Size: 32369 bytes Desc: image464079.PNG URL: From jakub at scholz.cz Thu Feb 21 20:52:40 2019 From: jakub at scholz.cz (Jakub Scholz) Date: Thu, 21 Feb 2019 21:52:40 +0100 Subject: [Strimzi] RC1 for Strimzi 0.11.0 Message-ID: Hi, The Release Candidate 1 for the Strimzi 0.11.0 release is now available. The main changes include: * Add support for JBOD storage for Kafka brokers * Allow users to configure the default ImagePullPolicy * Sample Prometheus alerts * More configuration options for off cluster access * Configure advertised hosts and ports * Configure NodePort numbers * Configure hosts OpenShift routes * Add additional DNS name for bootstrap service * and more. For more details and the upgrade procedure, go to: https://github.com/strimzi/strimzi-kafka-operator/releases/tag/0.10.0-rc2 Thanks & Regards Jakub -------------- next part -------------- An HTML attachment was scrubbed... URL: From jakub at scholz.cz Thu Feb 21 20:53:54 2019 From: jakub at scholz.cz (Jakub Scholz) Date: Thu, 21 Feb 2019 21:53:54 +0100 Subject: [Strimzi] RC1 for Strimzi 0.11.0 In-Reply-To: References: Message-ID: Of course there has to be wrong link ... the right one is here: https://github.com/strimzi/strimzi-kafka-operator/releases/tag/0.11.0-rc1 Thanks & Regards Jakub On Thu, Feb 21, 2019 at 9:52 PM Jakub Scholz wrote: > Hi, > > The Release Candidate 1 for the Strimzi 0.11.0 release is now available. > The main changes include: > * Add support for JBOD storage for Kafka brokers > * Allow users to configure the default ImagePullPolicy > * Sample Prometheus alerts > * More configuration options for off cluster access > * Configure advertised hosts and ports > * Configure NodePort numbers > * Configure hosts OpenShift routes > * Add additional DNS name for bootstrap service > * and more. > > For more details and the upgrade procedure, go to: > https://github.com/strimzi/strimzi-kafka-operator/releases/tag/0.10.0-rc2 > > Thanks & Regards > Jakub > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jakub at scholz.cz Fri Feb 22 17:44:23 2019 From: jakub at scholz.cz (Jakub Scholz) Date: Fri, 22 Feb 2019 18:44:23 +0100 Subject: [Strimzi] RC2 for Strimzi 0.11.0 Message-ID: Hi, The Release Candidate 2 for the first Strimzi 0.11.0 release is now available. It contain only minor changes and improvements compared to RC1. For more details and the upgrade procedure, go to: https://github.com/strimzi/strimzi-kafka-operator/releases/tag/0.11.0-rc2 Thanks & Regards Jakub -------------- next part -------------- An HTML attachment was scrubbed... URL: From jakub at scholz.cz Fri Feb 22 19:55:06 2019 From: jakub at scholz.cz (Jakub Scholz) Date: Fri, 22 Feb 2019 20:55:06 +0100 Subject: [Strimzi] Configure logging for kafka brokers In-Reply-To: <7f379179f07d403c89cb6c85980ba157@prosoz.de> References: <7f379179f07d403c89cb6c85980ba157@prosoz.de> Message-ID: Hi Markus, AFAIK log aggregation tooling usually doesn't work by reading the logs from files written inside the container. Instead it collects the output of the containers through the container runtime. For that reason you usually want to do the exact opposite of what you are asking for - write the logs only to STDOUT and not to files and let the infrastructure care of it. That is what is currently expected by Strimzi. I think you might be able to change the logging to file in configuration through config map. But Strimzi currently doesn't allow you to mount any volumes for the log files. Thanks & Regards Jakub On Fri, Feb 22, 2019 at 3:00 PM Schwarz, Markus wrote: > Hi, > > > > I?d like to have the kafka broker logs included in our log aggregation > tooling (Filebeat, Elasticsearch, Kibana) . For that to work I need the > broker logs to be written into a directory mounted as volume inside the > broker container. > > > > Now I got two problems: > > - How can I tell the broker where to put its logfiles? As I > understand the corresponding kafka configuration options are ?forbidden? in > strimzi. > > - How can I tell the operator to add a volume mount to the broker > pods? > > - Is there any other way to get the logs into elasticsearch? > > > > I?m using strimzi 0.9.0 at the moment, update to 0.10.0 will happen in the > next 3-4 weeks. > > > > Thanks, > > > > Markus > > > prosoz-herten-footer > _______________________________________________ > Strimzi mailing list > Strimzi at redhat.com > https://www.redhat.com/mailman/listinfo/strimzi > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image464079.PNG Type: image/png Size: 32369 bytes Desc: not available URL: From jakub at scholz.cz Mon Feb 25 20:39:24 2019 From: jakub at scholz.cz (Jakub Scholz) Date: Mon, 25 Feb 2019 21:39:24 +0100 Subject: [Strimzi] [Release] Strimzi 0.11.0 Message-ID: Strimzi 0.11.0 has been released. The main changes include: * Add support for JBOD storage for Kafka brokers * Allow users to configure the default ImagePullPolicy * Sample Prometheus alerts * More configuration options for off cluster access * Configure advertised hosts and ports * Configure NodePort numbers * Configure hosts OpenShift routes * Add additional DNS name for bootstrap service * Support for watching all namespaces * and many more. For more details go to http://strimzi.io/ and/or https://github.com/strimzi/strimzi-kafka-operator/releases/tag/0.11.0 Thanks to everyone who contributed to this release. Thanks & Regards Jakub -------------- next part -------------- An HTML attachment was scrubbed... URL: