databricks-kube-operator VS kube

Here's another example of a custom rust operator, https://github.com/mach-kernel/databricks-kube-operator

Written by a co-worker to help manage our databricks projects across clusters. Works wonderfully!!

So I used kube-rs and came up with this: https://github.com/mach-kernel/databricks-kube-operator

https://github.com/kube-rs/kube/blob/main/kube-client/src/api/portforward.rs ill create an issue and start working on implementing it. Thanks for the feedback

Interesting, I haven't tested that one yet. We use kube-rs (https://github.com/kube-rs/kube) under the hood, which does automatically token refresh when needed. But there might be some edge cases not considered.

So I used kube-rs and came up with this: https://github.com/mach-kernel/databricks-kube-operator

Stackable is building k8s operators in Rust for bringing up interconnectable, data crunching applications (being able to bring up a complete data platform on any k8s cluster is the goal). kube-rs is used under the hood and code is open source.

yes, we had a very small API to create who created role bindings for a CI. I chose Rust because it was easy and seems easily maintainable with the kube-rs https://github.com/kube-rs/kube-rs crate

I have experiencie on this. I'm a DevOps engineer that started before DevOps was a thing, and I want to write rust for a living. What I'm doing is writting rust for tooling and kubernetes controllers using https://github.com/kube-rs/kube-rs. Rust and DevOps are close specially if you need to write your own tools. My recommendation is if you have some space to solve problems at your job with rust go and do it, if not try some opensource projects that interest you to get more experience.