GitHub user chrsoo added a comment to the discussion: Pulsar Operator On Kubernetes
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? GitHub link: https://github.com/apache/pulsar/discussions/18398#discussioncomment-4103106 ---- This is an automatically sent email for dev@pulsar.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org
