You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by GitBox <gi...@apache.org> on 2022/11/10 01:51:30 UTC

[GitHub] [pulsar] sijie added a comment to the discussion: Pulsar Operator On Kubernetes

GitHub user sijie added a comment to the discussion: Pulsar Operator On Kubernetes

@chrsoo @sky-big @wolfstudy I think what @chrsoo request is an operator for the full lifecycle management for all the resources within a Pulsar instance. This includes both ClusterOperator and ResourceOperator. 

A ClusterOperator is what @sky-big is doing and most of the *operators* are doing. It is used for setting up a cluster and managing the upgrade, downgrade and scaling up-and-down a cluster.

A ResourceOperator is more about using *CRD* for provisioning *resources* within a Pulsar cluster. A *resource* such as a role (key and tokens), a tenant, a namespace, a topic, a function and etc. 

Once everything is modeled as CRD, you can use kubernetes to provision both cluster and resources. Thus you can apply a GitOps patten in a CI/CD pipeline to manage everything.

@chrsoo : this is kind of aligned with what we (StreamNative) are working on. We shall be able to share what we have done soon.

GitHub link: https://github.com/apache/pulsar/discussions/18398#discussioncomment-4103109

----
This is an automatically sent email for dev@pulsar.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@pulsar.apache.org