Hi Ethan Feng, Cheng Pan
1. More detail about the design, you can check this doc. https://github.com/xleoken/incubator-celeborn/blob/operator/operator/doc/design.md 2. Please consider providing minikube/k3s-based integration tests(or setup steps), Your suggestion is good. We can play with the celeborn-operator from the operator/operator/README.md doc currently. Sorry, I'm not familiar with minikube tests for now, maybe we can create a sub jira to finish it. Best, xleoken At 2023-11-08 17:20:49, "Ethan Feng" <[email protected]> wrote: >Hi xleoken, > >I completely agree with your idea. We can definitely use a Kubernetes >operator for Celeborn, and it would help us manage the Celeborn >clusters more effectively. > >Thank you for bringing this up, I found that you had already completed >the Kubernetes operator on your branch. Can you share your design docs >and contribute it to the community? > >Best regards, >Ethan Feng > >leo65535 <[email protected]> 于2023年11月8日周三 16:54写道： >> >> >> >> Hello everyone, >> >> >> As we known, kubernetes is designed for automation, Kubernetes' operator >> pattern concept >> lets you extend the cluster's behaviour without modifying the code of >> Kubernetes itself >> by linking controllers to one or more custom resources. Operators are >> clients of the >> Kubernetes API that act as controllers for a Custom Resource. >> >> >> So we can use k8s operator sdk to write our own operator for celeborn. the >> operator can >> help us to manage the celeborn clusters. >> >> >> Please check the jira[1] for more detail. >> >> >> Looking forward to your feedback and suggestions, thanks. >> >> >> Bests, >> xleoken >> >> >> [1] >> https://issues.apache.org/jira/browse/CELEBORN-1117 >>
