Hi Nick, I do not mean to derail your mail so I'll keep mine short: Yes, I think testing & infrastructure on Kubernetes would be worthwhile and I thank you for the offer. We're happy to take a look and would try to review any incoming contributions depending on how large/digestable they are :)
We[1] are developing our own operator[2] and during that mission have learned how prone Kubernetes is to bit rot so it'd be great if your team would continue helping out. I'm happy to go into details on why we did what we did but that'd be a separate thread. Cheers, Lars [1] <https://stackable.tech/en/> [2] <https://github.com/stackabletech/hbase-operator> On Tue, Mar 14, 2023 at 3:23 PM Mallikarjun <mallik.v.ar...@gmail.com> wrote: > > Hi Nick, > > I agree with your thought that there is an increasing reliance on > kubernetes, more so for complex workloads like hbase deployments because of > unavailability of reliable automation frameworks outside of k8s. > > But I have a slightly different view in terms of how to achieve it. When I > was exploring what are the possibilities such as kustomize or helm or > operator. I found it can get pretty complex in terms of writing extensible > deployment manifest (for different kinds of deployments) with tools like > kustomize or helm. Here is our attempt to conterairise hbase with operator > --> https://github.com/flipkart-incubator/hbase-k8s-operator > > --- > Mallikarjun > > On Mon, Mar 13, 2023 at 3:58 PM Nick Dimiduk <ndimi...@apache.org> wrote: > > > Heya team, > > > > Over here at $dayjob, we have an increasing reliance on Kubernetes for > > both development and production workloads. Our tools are maturing and > > we're hoping that they might be of interest to the wider community. > > I'd like to see if there's community interest in receiving some/any of > > them as a contribution. I think we'll also need a plan from ASF Infra > > that makes kubernetes available to us as a project. > > > > We have implemented a basic stack of tools for orchestrating ZK + HDFS > > + HBase on Kubernetes. We use this for running a small local dev > > cluster via MiniKube/KIND ; for ITBLL on smallish distributed clusters > > in a public cloud ; and in production for running clusters of ~100 > > Data Nodes/Region Servers in a public cloud. There was an earlier > > discussion about using our donation of test hardware for running more > > thorough tests in our CI, but one of the limiting factors is full > > cluster deployment. I hope that the community might be interested in > > receiving this tooling as a foundation for more rigorous correctness > > and maybe even performance tests in the open. Furthermore, perhaps the > > wider community has interest in an Apache licensed cluster > > orchestration tool for other uses. > > > > Now for some details: The implementation is built on Kustomize, so > > it's fundamentally transparent resource specification with yaml > > patches for composability; this is in contrast to a solution using > > templates with defined capabilities and interfaces. There is no > > operator ; it's all coordinated via init/bootstrap containers, shell > > scripts, shared volumes for state, &c. For now. > > > > Such a donation will amount to a code drop, which will have its > > challenges. I'm motivated via internal processes to carve it into > > smaller pieces, and I think that will benefit community review as > > well. Perhaps this approach could be used to make the contribution via > > a feature branch. > > > > Is there community interest in adding such a capability to our > > maintained responsibilities? I'd hope that we have several volunteers > > to work with me through the contribution process, and who are > > reasonably confident that they'll be able to help maintain such a > > capability going forward. We'll also need someone who can work with > > Infra to get us access to Kubernetes cluster(s), via whatever means. > > > > What do you think? > > > > Thanks, > > Nick & the HBase team at Apple
