pulsar-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [pulsar] chrsoo commented on issue #5534: Pulsar Operator On Kubernetes
Date Fri, 22 Nov 2019 18:22:09 GMT
chrsoo commented on issue #5534: Pulsar Operator On Kubernetes
URL: https://github.com/apache/pulsar/issues/5534#issuecomment-557638764
   The difficulty here is where to draw the line between more or less static configuration
and what should remain dynamically defined at runtime by the clients/users of the system.
This might vary in different contexts.
   I think it could be useful to define CRDs for the following Pulsar configuration items:
   1. **Tenants** with namespaces and their relation to Clusters
   1. **Persistent Topics** and their relation to tenants/namespaces
   1. **Sources** and **Sinks** and their relation to clusters/topics
   Starting with Tenants the following CRDs might be useful
   * **PulsarTenant** - defines a Pulsar Tenant
   * **PulsarNamespace** - defines a Pulsar Namespace for a Tenant
   * **PulsarNamespaceBinding** - binds a Pulsar Namespace to a PulsarCluster
   It would be good if Tenants and Namespaces are defined at the K8s cluster level as a Tenants
and Namespaces then could be reused across multiple PulsarClusters defined in the different
K8s namespaces. The PulsarNamespaceBinding should  be defined at the namespace level and in
the same namespace as the PulsarCluster to which it is bound.
   @sky-big - does all this make sense to you?

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

View raw message