On Thu, 2 May 2019, 09:26 Tom Bentley, <tbentley@...
On Wed, May 1, 2019 at 10:11 AM Alexis Richardson <alexis@...> wrote:
Kafka itself is not multi-tennant. Neither messages nor topics are owned authorised entities. So although it has different retention policies for messages, they're not associated with users or tenants. Rate limiting / quotas of connected clients are features of Kafka itself, rather than being something Strimzi adds. Therefore it might be hard
to separate it as a general concept.
Perhaps I misunderstood but isn't one goal of Strimzi to enable Kafka-aaS.
Strimzi provides operators which make it easy for different users to create their own Kafka clusters, (plus topics, users etc within those clusters). It does not provide support for a single Kafka cluster supporting multiple tenants. Obviously it is possible provide abstractions to do that on top of Kafka, but that's not what Strimzi provides.
Yes but what happens when there are two or more clusters? Does Strimzi support creation of multiple Kafka clusters in one kubernetes cluster? If so, then those clusters may require different user policies (even if Strimzi doesn't support that yet).