From jakub at scholz.cz Mon Mar 5 21:57:38 2018 From: jakub at scholz.cz (Jakub Scholz) Date: Mon, 5 Mar 2018 22:57:38 +0100 Subject: [Strimzi] RC1 of Strimzi 0.2.0 available Message-ID: Hi, I created Release Candidate 1 for the first Strimzi release - 0.2.0. If you are interested have a look at the release candidate and give us your feedback: https://github.com/strimzi/strimzi/releases/tag/v0.2.0-rc1 Thanks & Regards Jakub -------------- next part -------------- An HTML attachment was scrubbed... URL: From jakub at scholz.cz Tue Mar 6 15:03:45 2018 From: jakub at scholz.cz (Jakub Scholz) Date: Tue, 6 Mar 2018 16:03:45 +0100 Subject: [Strimzi] RC2 of Strimzi 0.2.0 available Message-ID: Hi, I created Release Candidate 2 for the first Strimzi release - 0.2.0. If you are interested have a look at the release candidate and give us your feedback: https://github.com/strimzi/strimzi/releases/tag/0.2.0-rc2 The changes since RC1 are: - Fix issues with RBAC enabled Kubernetes clusters (#286) - Fix NPE on Kubernetes caused by incorrectly triggered Kafka Connect S2I reconciliation (which is supported only on OpenShift) (#288) - Fix incorrectly released locks after cluster deletion (#280) Thanks & Regards Jakub -------------- next part -------------- An HTML attachment was scrubbed... URL: From shgriffi at redhat.com Tue Mar 6 14:58:29 2018 From: shgriffi at redhat.com (Sherard Griffin) Date: Tue, 6 Mar 2018 09:58:29 -0500 Subject: [Strimzi] Issue with Zookeeper PV when using GlusterFS Message-ID: Hi all, I'm trying to deploy an OpenWhisk project in OpenShift that uses Strimzi. I'm running into issues with the zookeeper PV. Because I'm using GlusterFS, the name gets too long and the PV can't be created. Can this be addressed? error: Invalid value: "glusterfs-dynamic-zookeeper-storage-strimzi-openwhisk-zookeeper-0": must be no more than 63 characters -- Thanks, Sherard Griffin -------------- next part -------------- An HTML attachment was scrubbed... URL: From ppatiern at redhat.com Tue Mar 6 15:25:53 2018 From: ppatiern at redhat.com (Paolo Patierno) Date: Tue, 6 Mar 2018 16:25:53 +0100 Subject: [Strimzi] Issue with Zookeeper PV when using GlusterFS In-Reply-To: References: Message-ID: Hi Sherard, we are using a volumeClaimTemplate named "zookeeper-storage" for the ZK StatefulSets definition and the name of the created PVCs has the following format : zookeeper-storage-[cluster-name]-zookeeper-[pod-id] It's interesting to see the "glusterfs-dynamic" at the beginning. Can you share how you configured GlusterFS please ? Thanks, Paolo. On Tue, Mar 6, 2018 at 3:58 PM, Sherard Griffin wrote: > Hi all, > > I'm trying to deploy an OpenWhisk project in OpenShift that uses Strimzi. > I'm running into issues with the zookeeper PV. Because I'm using > GlusterFS, the name gets too long and the PV can't be created. Can this be > addressed? > > error: Invalid value: "glusterfs-dynamic-zookeeper- > storage-strimzi-openwhisk-zookeeper-0": must be no more than 63 characters > > -- > Thanks, > Sherard Griffin > > _______________________________________________ > Strimzi mailing list > Strimzi at redhat.com > https://www.redhat.com/mailman/listinfo/strimzi > > -- PAOLO PATIERNO PRINCIPAL SOFTWARE ENGINEER, MESSAGING & IOT Red Hat -------------- next part -------------- An HTML attachment was scrubbed... URL: From jakub at scholz.cz Tue Mar 6 15:27:58 2018 From: jakub at scholz.cz (Jakub Scholz) Date: Tue, 6 Mar 2018 16:27:58 +0100 Subject: [Strimzi] Issue with Zookeeper PV when using GlusterFS In-Reply-To: References: Message-ID: Hi Sherard, What we can shorten quite easily is the middle part of the name which is "zookeeper-storage" or "kafka-storage". We can use something like "data" instead. That should get you under 63 characters. The "glusterfs-dynamic-" prefix is something what I assume we cannot affect. The the "-strimzi-openwhisk-zookeeper-0" should be the pod name. We can in theory make that slightly shorter as well if needed. But lets start with the middle section first. I created an issue for it ( https://github.com/strimzi/strimzi/issues/294) and will have a look at it. Thanks & Regards Jakub On Tue, Mar 6, 2018 at 3:58 PM, Sherard Griffin wrote: > Hi all, > > I'm trying to deploy an OpenWhisk project in OpenShift that uses Strimzi. > I'm running into issues with the zookeeper PV. Because I'm using > GlusterFS, the name gets too long and the PV can't be created. Can this be > addressed? > > error: Invalid value: "glusterfs-dynamic-zookeeper- > storage-strimzi-openwhisk-zookeeper-0": must be no more than 63 characters > > -- > Thanks, > Sherard Griffin > > _______________________________________________ > Strimzi mailing list > Strimzi at redhat.com > https://www.redhat.com/mailman/listinfo/strimzi > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bbrownin at redhat.com Tue Mar 6 15:52:56 2018 From: bbrownin at redhat.com (Ben Browning) Date: Tue, 6 Mar 2018 10:52:56 -0500 Subject: [Strimzi] Issue with Zookeeper PV when using GlusterFS In-Reply-To: References: Message-ID: And, on our end, we can shorten "strimzi-openwhisk" (the name coming from our template) down to something quite a bit shorter. The only reason it's that long is because that's the name of the configmap defining the kafka cluster so we didn't want it to be too generic. On Tue, Mar 6, 2018 at 10:27 AM, Jakub Scholz wrote: > Hi Sherard, > > What we can shorten quite easily is the middle part of the name which is > "zookeeper-storage" or "kafka-storage". We can use something like "data" > instead. That should get you under 63 characters. The "glusterfs-dynamic-" > prefix is something what I assume we cannot affect. The the > "-strimzi-openwhisk-zookeeper-0" should be the pod name. We can in theory > make that slightly shorter as well if needed. But lets start with the middle > section first. I created an issue for it > (https://github.com/strimzi/strimzi/issues/294) and will have a look at it. > > Thanks & Regards > Jakub > > On Tue, Mar 6, 2018 at 3:58 PM, Sherard Griffin wrote: >> >> Hi all, >> >> I'm trying to deploy an OpenWhisk project in OpenShift that uses Strimzi. >> I'm running into issues with the zookeeper PV. Because I'm using GlusterFS, >> the name gets too long and the PV can't be created. Can this be addressed? >> >> error: Invalid value: >> "glusterfs-dynamic-zookeeper-storage-strimzi-openwhisk-zookeeper-0": must be >> no more than 63 characters >> >> -- >> Thanks, >> Sherard Griffin >> >> _______________________________________________ >> Strimzi mailing list >> Strimzi at redhat.com >> https://www.redhat.com/mailman/listinfo/strimzi >> > From shgriffi at redhat.com Tue Mar 6 17:10:36 2018 From: shgriffi at redhat.com (Sherard Griffin) Date: Tue, 6 Mar 2018 12:10:36 -0500 Subject: [Strimzi] Issue with Zookeeper PV when using GlusterFS In-Reply-To: References: Message-ID: It definitely seems like the gluster part is added on by default. If you try this yaml, it'll result in the issue. Notice I don't add the gluster part to the front of the name, OpenShift does that. apiVersion: v1 kind: PersistentVolumeClaim metadata: name: zookeeper-storage-strimzi-openwhisk-zookeeper-0 namespace: dh-stage-owisk2 spec: accessModes: - ReadWriteOnce storageClassName: glusterfs-apps resources: requests: storage: 1Gi On Tue, Mar 6, 2018 at 10:52 AM, Ben Browning wrote: > And, on our end, we can shorten "strimzi-openwhisk" (the name coming > from our template) down to something quite a bit shorter. The only > reason it's that long is because that's the name of the configmap > defining the kafka cluster so we didn't want it to be too generic. > > On Tue, Mar 6, 2018 at 10:27 AM, Jakub Scholz wrote: > > Hi Sherard, > > > > What we can shorten quite easily is the middle part of the name which is > > "zookeeper-storage" or "kafka-storage". We can use something like "data" > > instead. That should get you under 63 characters. The > "glusterfs-dynamic-" > > prefix is something what I assume we cannot affect. The the > > "-strimzi-openwhisk-zookeeper-0" should be the pod name. We can in > theory > > make that slightly shorter as well if needed. But lets start with the > middle > > section first. I created an issue for it > > (https://github.com/strimzi/strimzi/issues/294) and will have a look at > it. > > > > Thanks & Regards > > Jakub > > > > On Tue, Mar 6, 2018 at 3:58 PM, Sherard Griffin > wrote: > >> > >> Hi all, > >> > >> I'm trying to deploy an OpenWhisk project in OpenShift that uses > Strimzi. > >> I'm running into issues with the zookeeper PV. Because I'm using > GlusterFS, > >> the name gets too long and the PV can't be created. Can this be > addressed? > >> > >> error: Invalid value: > >> "glusterfs-dynamic-zookeeper-storage-strimzi-openwhisk-zookeeper-0": > must be > >> no more than 63 characters > >> > >> -- > >> Thanks, > >> Sherard Griffin > >> > >> _______________________________________________ > >> Strimzi mailing list > >> Strimzi at redhat.com > >> https://www.redhat.com/mailman/listinfo/strimzi > >> > > > -- Thanks, Sherard Griffin -------------- next part -------------- An HTML attachment was scrubbed... URL: From ppatiern at redhat.com Tue Mar 6 17:21:13 2018 From: ppatiern at redhat.com (Paolo Patierno) Date: Tue, 6 Mar 2018 18:21:13 +0100 Subject: [Strimzi] Issue with Zookeeper PV when using GlusterFS In-Reply-To: References: Message-ID: Yes as Jakub described in the related issue, it should be the storage provider name (for the specified storage class). On Tue, Mar 6, 2018 at 6:10 PM, Sherard Griffin wrote: > It definitely seems like the gluster part is added on by default. If you > try this yaml, it'll result in the issue. Notice I don't add the gluster > part to the front of the name, OpenShift does that. > > apiVersion: v1 > kind: PersistentVolumeClaim > metadata: > name: zookeeper-storage-strimzi-openwhisk-zookeeper-0 > namespace: dh-stage-owisk2 > spec: > accessModes: > - ReadWriteOnce > storageClassName: glusterfs-apps > resources: > requests: > storage: 1Gi > > > On Tue, Mar 6, 2018 at 10:52 AM, Ben Browning wrote: > >> And, on our end, we can shorten "strimzi-openwhisk" (the name coming >> from our template) down to something quite a bit shorter. The only >> reason it's that long is because that's the name of the configmap >> defining the kafka cluster so we didn't want it to be too generic. >> >> On Tue, Mar 6, 2018 at 10:27 AM, Jakub Scholz wrote: >> > Hi Sherard, >> > >> > What we can shorten quite easily is the middle part of the name which is >> > "zookeeper-storage" or "kafka-storage". We can use something like "data" >> > instead. That should get you under 63 characters. The >> "glusterfs-dynamic-" >> > prefix is something what I assume we cannot affect. The the >> > "-strimzi-openwhisk-zookeeper-0" should be the pod name. We can in >> theory >> > make that slightly shorter as well if needed. But lets start with the >> middle >> > section first. I created an issue for it >> > (https://github.com/strimzi/strimzi/issues/294) and will have a look >> at it. >> > >> > Thanks & Regards >> > Jakub >> > >> > On Tue, Mar 6, 2018 at 3:58 PM, Sherard Griffin >> wrote: >> >> >> >> Hi all, >> >> >> >> I'm trying to deploy an OpenWhisk project in OpenShift that uses >> Strimzi. >> >> I'm running into issues with the zookeeper PV. Because I'm using >> GlusterFS, >> >> the name gets too long and the PV can't be created. Can this be >> addressed? >> >> >> >> error: Invalid value: >> >> "glusterfs-dynamic-zookeeper-storage-strimzi-openwhisk-zookeeper-0": >> must be >> >> no more than 63 characters >> >> >> >> -- >> >> Thanks, >> >> Sherard Griffin >> >> >> >> _______________________________________________ >> >> Strimzi mailing list >> >> Strimzi at redhat.com >> >> https://www.redhat.com/mailman/listinfo/strimzi >> >> >> > >> > > > > -- > Thanks, > Sherard Griffin > > _______________________________________________ > Strimzi mailing list > Strimzi at redhat.com > https://www.redhat.com/mailman/listinfo/strimzi > > -- PAOLO PATIERNO PRINCIPAL SOFTWARE ENGINEER, MESSAGING & IOT Red Hat -------------- next part -------------- An HTML attachment was scrubbed... URL: From shgriffi at redhat.com Tue Mar 6 17:33:20 2018 From: shgriffi at redhat.com (Sherard Griffin) Date: Tue, 6 Mar 2018 12:33:20 -0500 Subject: [Strimzi] Issue with Zookeeper PV when using GlusterFS In-Reply-To: References: Message-ID: How can we track this issue? Through the git project? On Tue, Mar 6, 2018 at 12:21 PM, Paolo Patierno wrote: > Yes as Jakub described in the related issue, it should be the storage > provider name (for the specified storage class). > > On Tue, Mar 6, 2018 at 6:10 PM, Sherard Griffin > wrote: > >> It definitely seems like the gluster part is added on by default. If you >> try this yaml, it'll result in the issue. Notice I don't add the gluster >> part to the front of the name, OpenShift does that. >> >> apiVersion: v1 >> kind: PersistentVolumeClaim >> metadata: >> name: zookeeper-storage-strimzi-openwhisk-zookeeper-0 >> namespace: dh-stage-owisk2 >> spec: >> accessModes: >> - ReadWriteOnce >> storageClassName: glusterfs-apps >> resources: >> requests: >> storage: 1Gi >> >> >> On Tue, Mar 6, 2018 at 10:52 AM, Ben Browning >> wrote: >> >>> And, on our end, we can shorten "strimzi-openwhisk" (the name coming >>> from our template) down to something quite a bit shorter. The only >>> reason it's that long is because that's the name of the configmap >>> defining the kafka cluster so we didn't want it to be too generic. >>> >>> On Tue, Mar 6, 2018 at 10:27 AM, Jakub Scholz wrote: >>> > Hi Sherard, >>> > >>> > What we can shorten quite easily is the middle part of the name which >>> is >>> > "zookeeper-storage" or "kafka-storage". We can use something like >>> "data" >>> > instead. That should get you under 63 characters. The >>> "glusterfs-dynamic-" >>> > prefix is something what I assume we cannot affect. The the >>> > "-strimzi-openwhisk-zookeeper-0" should be the pod name. We can in >>> theory >>> > make that slightly shorter as well if needed. But lets start with the >>> middle >>> > section first. I created an issue for it >>> > (https://github.com/strimzi/strimzi/issues/294) and will have a look >>> at it. >>> > >>> > Thanks & Regards >>> > Jakub >>> > >>> > On Tue, Mar 6, 2018 at 3:58 PM, Sherard Griffin >>> wrote: >>> >> >>> >> Hi all, >>> >> >>> >> I'm trying to deploy an OpenWhisk project in OpenShift that uses >>> Strimzi. >>> >> I'm running into issues with the zookeeper PV. Because I'm using >>> GlusterFS, >>> >> the name gets too long and the PV can't be created. Can this be >>> addressed? >>> >> >>> >> error: Invalid value: >>> >> "glusterfs-dynamic-zookeeper-storage-strimzi-openwhisk-zookeeper-0": >>> must be >>> >> no more than 63 characters >>> >> >>> >> -- >>> >> Thanks, >>> >> Sherard Griffin >>> >> >>> >> _______________________________________________ >>> >> Strimzi mailing list >>> >> Strimzi at redhat.com >>> >> https://www.redhat.com/mailman/listinfo/strimzi >>> >> >>> > >>> >> >> >> >> -- >> Thanks, >> Sherard Griffin >> >> _______________________________________________ >> Strimzi mailing list >> Strimzi at redhat.com >> https://www.redhat.com/mailman/listinfo/strimzi >> >> > > > -- > > PAOLO PATIERNO > > PRINCIPAL SOFTWARE ENGINEER, MESSAGING & IOT > > Red Hat > > > > > -- Thanks, Sherard Griffin -------------- next part -------------- An HTML attachment was scrubbed... URL: From ppatiern at redhat.com Tue Mar 6 17:35:03 2018 From: ppatiern at redhat.com (Paolo Patierno) Date: Tue, 6 Mar 2018 18:35:03 +0100 Subject: [Strimzi] Issue with Zookeeper PV when using GlusterFS In-Reply-To: References: Message-ID: Jakub opened this one (https://github.com/strimzi/strimzi/issues/294) which is already fixed in the master now. At least we have reduced on our side from zookeeper-storage or kafka-storage to just "data", On Tue, Mar 6, 2018 at 6:33 PM, Sherard Griffin wrote: > How can we track this issue? Through the git project? > > On Tue, Mar 6, 2018 at 12:21 PM, Paolo Patierno > wrote: > >> Yes as Jakub described in the related issue, it should be the storage >> provider name (for the specified storage class). >> >> On Tue, Mar 6, 2018 at 6:10 PM, Sherard Griffin >> wrote: >> >>> It definitely seems like the gluster part is added on by default. If >>> you try this yaml, it'll result in the issue. Notice I don't add the >>> gluster part to the front of the name, OpenShift does that. >>> >>> apiVersion: v1 >>> kind: PersistentVolumeClaim >>> metadata: >>> name: zookeeper-storage-strimzi-openwhisk-zookeeper-0 >>> namespace: dh-stage-owisk2 >>> spec: >>> accessModes: >>> - ReadWriteOnce >>> storageClassName: glusterfs-apps >>> resources: >>> requests: >>> storage: 1Gi >>> >>> >>> On Tue, Mar 6, 2018 at 10:52 AM, Ben Browning >>> wrote: >>> >>>> And, on our end, we can shorten "strimzi-openwhisk" (the name coming >>>> from our template) down to something quite a bit shorter. The only >>>> reason it's that long is because that's the name of the configmap >>>> defining the kafka cluster so we didn't want it to be too generic. >>>> >>>> On Tue, Mar 6, 2018 at 10:27 AM, Jakub Scholz wrote: >>>> > Hi Sherard, >>>> > >>>> > What we can shorten quite easily is the middle part of the name which >>>> is >>>> > "zookeeper-storage" or "kafka-storage". We can use something like >>>> "data" >>>> > instead. That should get you under 63 characters. The >>>> "glusterfs-dynamic-" >>>> > prefix is something what I assume we cannot affect. The the >>>> > "-strimzi-openwhisk-zookeeper-0" should be the pod name. We can in >>>> theory >>>> > make that slightly shorter as well if needed. But lets start with the >>>> middle >>>> > section first. I created an issue for it >>>> > (https://github.com/strimzi/strimzi/issues/294) and will have a look >>>> at it. >>>> > >>>> > Thanks & Regards >>>> > Jakub >>>> > >>>> > On Tue, Mar 6, 2018 at 3:58 PM, Sherard Griffin >>>> wrote: >>>> >> >>>> >> Hi all, >>>> >> >>>> >> I'm trying to deploy an OpenWhisk project in OpenShift that uses >>>> Strimzi. >>>> >> I'm running into issues with the zookeeper PV. Because I'm using >>>> GlusterFS, >>>> >> the name gets too long and the PV can't be created. Can this be >>>> addressed? >>>> >> >>>> >> error: Invalid value: >>>> >> "glusterfs-dynamic-zookeeper-storage-strimzi-openwhisk-zookeeper-0": >>>> must be >>>> >> no more than 63 characters >>>> >> >>>> >> -- >>>> >> Thanks, >>>> >> Sherard Griffin >>>> >> >>>> >> _______________________________________________ >>>> >> Strimzi mailing list >>>> >> Strimzi at redhat.com >>>> >> https://www.redhat.com/mailman/listinfo/strimzi >>>> >> >>>> > >>>> >>> >>> >>> >>> -- >>> Thanks, >>> Sherard Griffin >>> >>> _______________________________________________ >>> Strimzi mailing list >>> Strimzi at redhat.com >>> https://www.redhat.com/mailman/listinfo/strimzi >>> >>> >> >> >> -- >> >> PAOLO PATIERNO >> >> PRINCIPAL SOFTWARE ENGINEER, MESSAGING & IOT >> >> Red Hat >> >> >> >> >> > > > > -- > Thanks, > Sherard Griffin > -- PAOLO PATIERNO PRINCIPAL SOFTWARE ENGINEER, MESSAGING & IOT Red Hat -------------- next part -------------- An HTML attachment was scrubbed... URL: From shgriffi at redhat.com Tue Mar 6 17:51:11 2018 From: shgriffi at redhat.com (Sherard Griffin) Date: Tue, 6 Mar 2018 12:51:11 -0500 Subject: [Strimzi] Issue with Zookeeper PV when using GlusterFS In-Reply-To: References: Message-ID: Awesome, thanks guys! I'll test this as soon as I get some permissions fixed on my environment. On Tue, Mar 6, 2018 at 12:35 PM, Paolo Patierno wrote: > Jakub opened this one (https://github.com/strimzi/strimzi/issues/294) > which is already fixed in the master now. At least we have reduced on our > side from zookeeper-storage or kafka-storage to just "data", > > On Tue, Mar 6, 2018 at 6:33 PM, Sherard Griffin > wrote: > >> How can we track this issue? Through the git project? >> >> On Tue, Mar 6, 2018 at 12:21 PM, Paolo Patierno >> wrote: >> >>> Yes as Jakub described in the related issue, it should be the storage >>> provider name (for the specified storage class). >>> >>> On Tue, Mar 6, 2018 at 6:10 PM, Sherard Griffin >>> wrote: >>> >>>> It definitely seems like the gluster part is added on by default. If >>>> you try this yaml, it'll result in the issue. Notice I don't add the >>>> gluster part to the front of the name, OpenShift does that. >>>> >>>> apiVersion: v1 >>>> kind: PersistentVolumeClaim >>>> metadata: >>>> name: zookeeper-storage-strimzi-openwhisk-zookeeper-0 >>>> namespace: dh-stage-owisk2 >>>> spec: >>>> accessModes: >>>> - ReadWriteOnce >>>> storageClassName: glusterfs-apps >>>> resources: >>>> requests: >>>> storage: 1Gi >>>> >>>> >>>> On Tue, Mar 6, 2018 at 10:52 AM, Ben Browning >>>> wrote: >>>> >>>>> And, on our end, we can shorten "strimzi-openwhisk" (the name coming >>>>> from our template) down to something quite a bit shorter. The only >>>>> reason it's that long is because that's the name of the configmap >>>>> defining the kafka cluster so we didn't want it to be too generic. >>>>> >>>>> On Tue, Mar 6, 2018 at 10:27 AM, Jakub Scholz wrote: >>>>> > Hi Sherard, >>>>> > >>>>> > What we can shorten quite easily is the middle part of the name >>>>> which is >>>>> > "zookeeper-storage" or "kafka-storage". We can use something like >>>>> "data" >>>>> > instead. That should get you under 63 characters. The >>>>> "glusterfs-dynamic-" >>>>> > prefix is something what I assume we cannot affect. The the >>>>> > "-strimzi-openwhisk-zookeeper-0" should be the pod name. We can in >>>>> theory >>>>> > make that slightly shorter as well if needed. But lets start with >>>>> the middle >>>>> > section first. I created an issue for it >>>>> > (https://github.com/strimzi/strimzi/issues/294) and will have a >>>>> look at it. >>>>> > >>>>> > Thanks & Regards >>>>> > Jakub >>>>> > >>>>> > On Tue, Mar 6, 2018 at 3:58 PM, Sherard Griffin >>>>> wrote: >>>>> >> >>>>> >> Hi all, >>>>> >> >>>>> >> I'm trying to deploy an OpenWhisk project in OpenShift that uses >>>>> Strimzi. >>>>> >> I'm running into issues with the zookeeper PV. Because I'm using >>>>> GlusterFS, >>>>> >> the name gets too long and the PV can't be created. Can this be >>>>> addressed? >>>>> >> >>>>> >> error: Invalid value: >>>>> >> "glusterfs-dynamic-zookeeper-storage-strimzi-openwhisk-zookeeper-0": >>>>> must be >>>>> >> no more than 63 characters >>>>> >> >>>>> >> -- >>>>> >> Thanks, >>>>> >> Sherard Griffin >>>>> >> >>>>> >> _______________________________________________ >>>>> >> Strimzi mailing list >>>>> >> Strimzi at redhat.com >>>>> >> https://www.redhat.com/mailman/listinfo/strimzi >>>>> >> >>>>> > >>>>> >>>> >>>> >>>> >>>> -- >>>> Thanks, >>>> Sherard Griffin >>>> >>>> _______________________________________________ >>>> Strimzi mailing list >>>> Strimzi at redhat.com >>>> https://www.redhat.com/mailman/listinfo/strimzi >>>> >>>> >>> >>> >>> -- >>> >>> PAOLO PATIERNO >>> >>> PRINCIPAL SOFTWARE ENGINEER, MESSAGING & IOT >>> >>> Red Hat >>> >>> >>> >>> >>> >> >> >> >> -- >> Thanks, >> Sherard Griffin >> > > > > -- > > PAOLO PATIERNO > > PRINCIPAL SOFTWARE ENGINEER, MESSAGING & IOT > > Red Hat > > > > > -- Thanks, Sherard Griffin -------------- next part -------------- An HTML attachment was scrubbed... URL: From jakub at scholz.cz Wed Mar 7 11:48:35 2018 From: jakub at scholz.cz (Jakub Scholz) Date: Wed, 7 Mar 2018 12:48:35 +0100 Subject: [Strimzi] RC3 of Strimzi 0.2.0 available Message-ID: Hi, Hopefully this is the last set of bugs. The RC3 also updated Kafka to 1.0.1. If you are interested have a look at the release candidate and give us your feedback: https://github.com/strimzi/strimzi/releases/tag/0.2.0-rc3 Changes since rc2: - Release lock when periodic reconcile is freed after ongoing deletion #296 - Persistent Volume name too long #294 - Update to Kafka 1.0.1 #242 Thanks & Regards Jakub -------------- next part -------------- An HTML attachment was scrubbed... URL: From ppatiern at redhat.com Thu Mar 8 10:59:39 2018 From: ppatiern at redhat.com (Paolo Patierno) Date: Thu, 8 Mar 2018 11:59:39 +0100 Subject: [Strimzi] RC3 of Strimzi 0.2.0 available In-Reply-To: References: Message-ID: +1 from me Deployed on Minikube and Minishift with 3 Zookeeper nodes + 3 Kafka brokers + 1 Kafka Connect node I was able to send and receive messages. On Wed, Mar 7, 2018 at 12:48 PM, Jakub Scholz wrote: > Hi, > > Hopefully this is the last set of bugs. The RC3 also updated Kafka to > 1.0.1. > > If you are interested have a look at the release candidate and give us > your feedback: > https://github.com/strimzi/strimzi/releases/tag/0.2.0-rc3 > > Changes since rc2: > - Release lock when periodic reconcile is freed after ongoing deletion #296 > - Persistent Volume name too long #294 > - Update to Kafka 1.0.1 #242 > > Thanks & Regards > Jakub > > _______________________________________________ > Strimzi mailing list > Strimzi at redhat.com > https://www.redhat.com/mailman/listinfo/strimzi > > -- PAOLO PATIERNO PRINCIPAL SOFTWARE ENGINEER, MESSAGING & IOT Red Hat -------------- next part -------------- An HTML attachment was scrubbed... URL: From jakub at scholz.cz Fri Mar 9 11:02:15 2018 From: jakub at scholz.cz (Jakub Scholz) Date: Fri, 9 Mar 2018 12:02:15 +0100 Subject: [Strimzi] [Release] Strimzi 0.2.0 Message-ID: Strimzi 0.2.0 is now available. The main changes are: - New operator concept with Cluster Controller and Topic Controller - Custer Controller is responsible for deployment of Kafka and Kafka Connect clusters - Topic Controller is managing Kafka Topics - Improved documentation - Improved examples - Docker images based on CentOS 7 - Improved test coverage - Update to Kafka 1.0.1 For more details go to http://strimzi.io/ and/or https://github.com/strimzi/strimzi/releases/tag/0.2.0 Thanks to everyone who help with this release. Jakub -------------- next part -------------- An HTML attachment was scrubbed... URL: