You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2019/11/24 05:52:53 UTC

[GitHub] [pulsar] sijie commented on issue #5534: Pulsar Operator On Kubernetes

sijie commented on issue #5534: Pulsar Operator On Kubernetes
URL: https://github.com/apache/pulsar/issues/5534#issuecomment-557860442
 
 
   @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.

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services