kube VS winsafe

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.

I know all that shit because I'm the author of Rust's WinSafe library, which is a safer Rust layer over native Win32, so I had to deal with a lot of shit like this.

[dependencies] winsafe = { git = "https://github.com/rodrigocfd/winsafe", features = ["kernel"] }

Externally, you can write a lot of native Windows stuff in Rust already. Personally, I'm having a lot of fun with WinSafe.

If you had such problems (which I also had in the past), I'm really interested in you opinion about WinSafe, and if it could help you solving them.

If you're after a native Windows application, WinSafe may suit your needs.

As the author of WinSafe, I can say it's tedious sometimes, but it's often very challenging, because you have to translate crazy unsafe behaviors into Rust's ownership model. It's surely hard, but also very rewarding at the end.

As the author of the WinSafe lib, I wholeheartedly agree.

I don't know how rare this is (or how rare it should be), but this issue warned me about this potential problem, and I had to make a huge refactoring to treat the possibility. I had to rethink many aspects of all handle implementations. It was hard work, but in the end it was worth it.

WinSafe says hello.

WinSafe, for example (which attemps to be a safe layer over the Windows API), provides lots of RAII automations. A fine example is the BeginPaint function: