Thank you very much for your proposal. I have also had the same idea for some time. Currently, seata-server is stateless, so it can be deployed using deployment in the official documentation. With the evolution of 2.x, Seata will introduce raft's cluster mode, which will be applicable to statefulsets. How to help businesses quickly maintain and reduce the cost of operations is an important means of helping Seata quickly become popular.

非常感谢你的提议。我也一直有同样的想法，目前seata-server是无状态的，因此在官网的文档上是可以用deployment来部署的。随着2.x的演进，Seata将加入raft的集群模式，对satefulset的应用，如何快速帮助业务去运维，降低运维的成本，是帮助Seata快速普及的重要手段。

What operational capabilities can Seata operator provide to seata-server in the current version?

在当前的版本中，operator可以为seata-server提供哪些运维或增强能力？

What operational capabilities can Seata operator provide to seata-server in the current version?

在当前的版本中，operator可以为seata-server提供哪些运维或增强能力？

Some benefits of operator:

• Easy to understand and manage resource: normally, a service need a k8s deployment and a k8s service work together, in operator we can create a CRD to let all in one resources, we can directly detect the status and others.
• More auto operations: base on CR, we can do auto operation in the operator, for example, auto restart, keep cluster up and so on.
• Multi-cluster ability: we can use operator to deploy cluster mode of service in different k8s cluster for high availability
• ...

And there are lots of use cases we can support in future.

For now, I think a very easy operator to manage Deployment and Service is a good start for us.

@wilsonwu You can submit PR to this repo https://github.com/seata/seata-k8s .

Your contribution is very welcome, in stateful raft storage mode, one has to get the full ip list and ports of the cluster before starting the Seata-Server process, which is exactly what is needed for the k8s operator's capabilities, unfortunately at the moment #5226 is not yet merged
非常欢迎你的贡献，在有状态的raft存储模式下，必须得到完整的集群的ip列表和端口之后，才能启动Seata-Server的进程，这正是需要k8s operator的能力，遗憾的是目前 #5226 还未合并

Your contribution is very welcome, in stateful raft storage mode, one has to get the full ip list and ports of the cluster before starting the Seata-Server process, which is exactly what is needed for the k8s operator's capabilities, unfortunately at the moment #5226 is not yet merged 非常欢迎你的贡献，在有状态的raft存储模式下，必须得到完整的集群的ip列表和端口之后，才能启动Seata-Server的进程，这正是需要k8s operator的能力，遗憾的是目前 #5226 还未合并

Thanks for your message, I will notice that in our internal seats-operator (currently not open sources) logic.