Hi team, I am reaching out to discuss a potential enhancement to our current toolset, specifically focusing on the integration of K8s cluster operating capabilities into seata-ctl.
seata-ctl serves as a command-line interface tool for minimizing transaction operation overhead. I believe there is an opportunity to extend its functionalities to assist users in operating seata-server within a Kubernetes cluster more efficiently. The proposed features would include the ability to create, delete, and list namespaces/clusters. The key benefits of implementing such features are: 1. Enhanced User Experience: By incorporating K8s cluster operating capabilities into seata-ctl, we would allow users to manage seata-server instances and related resources more conveniently. 2. Consistency and Integration: Integrating these features into seata-ctl ensures a unified interface for users, maintaining consistency across different operations and reducing the learning curve. This approach also promotes better integration with existing tooling. I would like to discuss about whether we should implement such features. And also, the question arises regarding the implementation strategy. I suppose there are at least two potential options: 1. seata-ctl extension: We can integrate the K8s cluster operating capabilities directly into the existing seata-ctl tool. This approach would involve extending the functionalities of the current command-line interface to encompass the new features. 2. seata-k8s cli-tool: Alternatively, we could create a dedicated command-line tool within the seata-k8s repository, independent of seata-ctl. This would involve developing a separate tool specifically designed for managing seata-server instances in a Kubernetes environment. Looking forward to your feedback on whether and how we should implement it, to extend seata-ctl or develop a standalone tool in seata-k8s. Thank you for your time and consideration. Best regards, Xiangkun Yin (ptyin)
