[Strimzi] RC1 of Strimzi 0.3.0 available

[Jakub Scholz]

One of the problems is that the config map is a namespaced resource. But if
you want a Kafka cluster which serves multiple namespaces then Kafka topic
is not namespaced resource. That means a lot of complications. For example
what should we do when the same topic is configured within different
namespaces? So I do not think we can see the presence of the config map for
given topic in the namespace as a proof of ownership for the topic.

I think that the general idea is quite good. But the implementation might
not be trivial. I think I will need some more time to think about it.
Either way this is far beyond the 0.3.0 scope.

Thanks
Jakub


On Mon, Apr 16, 2018 at 10:24 AM, Budzik, Przemyslaw <
Przemyslaw.Budzik at sabre.com> wrote:

> Thank you Jakub. I have a question. Is there any way to bind namespace
> with topic in terms of authorization? Consider a scenario.
>
>
>
>    1. Team A creates a topic called “reservations”. They own the config
>    map and of course they can publish to this topic.
>    2. Team B is interested in consuming A’s messages. I am guessing if
>    they know the name of the topic, they can use it ? Ideally since they are
>    in the namespace B, we’d like to be able to say they can, but others
>    can’t.  Also I mean we give them read, but not write. Most likely it’s the
>    creator of topic writing and other namespaces (or the same) consuming.
>
>
>
> If that is not supported, is that on your roadmap ?
>
>
>
> *From:* Jakub Scholz [mailto:jakub at scholz.cz]
> *Sent:* Friday, April 13, 2018 2:44 PM
> *To:* Budzik, Przemyslaw <Przemyslaw.Budzik at sabre.com>
> *Cc:* strimzi at redhat.com; Chylek, Artur <Artur.Chylek at sabre.com>; Wnuk,
> Norbert <Norbert.Wnuk at sabre.com>
> *Subject:* Re: [Strimzi] RC1 of Strimzi 0.3.0 available
>
>
>
> Hi,
>
>
>
> Well, it is a release candidate. So while I hope that there will be no
> issues, there is always possibility. But feel free to give it a try. It
> doesn't bring any significant new features, but it improves a bit the
> resilience with which the controller reacts to different problems and
> situations. If you didn't experienced any issues with 0.2.0, you can just
> stay with it.
>
>
>
> I hope the final release will be done early next week.
>
>
>
> Thanks & Regards
>
> Jakub
>
>
>
> On Fri, Apr 13, 2018 at 1:10 AM, Budzik, Przemyslaw <
> Przemyslaw.Budzik at sabre.com> wrote:
>
> Jakub,
>
>
>
> Which version would you recommend using in our case ? One of the teams is
> now installing Strimzi in our DEV environment.
>
>
>
> Thanks,
>
> Przemek
>
>
>
> *From:* strimzi-bounces at redhat.com [mailto:strimzi-bounces at redhat.com] *On
> Behalf Of *Jakub Scholz
> *Sent:* Friday, April 13, 2018 4:32 AM
> *To:* strimzi at redhat.com
> *Subject:* [Strimzi] RC1 of Strimzi 0.3.0 available
>
>
>
> Hi,
>
>
>
> The Release Candidate 1 for the first Strimzi 0.3.0 is now available.
>
>
>
> If you are interested have a look at the release candidate and give us
> your feedback:
>
> https://github.com/strimzi/strimzi/releases/tag/0.3.0-rc1
>
>
>
> Thanks & Regards
>
> Jakub
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/strimzi/attachments/20180417/43ce7d57/attachment.htm>