[NEOS-1358] Kubernetes Operator

[mcanevet]

I was excited to discover that I could describe my jobs as code using the Terraform provider for NeoSync. This is a fantastic feature! However, I started thinking about how useful it would be to have similar functionality with Kubernetes objects. As a platform engineer, my team strives to offer Kubernetes-native solutions to our users for consistency and ease of use.

While researching, I came across a blog post that mentioned the idea of a NeoSync Kubernetes Operator, which initially made me very excited. However, I was disappointed to read that this idea was dropped because of concerns about limiting the project to the Kubernetes ecosystem. I completely agree that NeoSync should remain flexible and not be tightly coupled with Kubernetes.

That said, I believe there could be value in providing a Kubernetes Operator as an optional, side project. This approach would allow NeoSync to stay agnostic while still offering Kubernetes-native integrations for teams like mine who heavily rely on Kubernetes. Many projects successfully provide such operators as optional add-ons, ensuring that their core functionality remains independent of Kubernetes.

Would it be possible to consider developing a NeoSync Kubernetes Operator as an optional feature? This would greatly benefit platform teams who are working in Kubernetes-centric environments.

_NEOS-1358

[nickzelei]

Hey thanks for the feature request!

We could definitely get it added to our roadmap which would help us gauge interest and prioritize.

[mcanevet]

@nickzelei a Crossplane provider for NeoSync would also do the trick.
We could leverage upjet to generate it from the Terraform provider.

[evisdrenova]

@mcanevet sounds pretty interesting. Will do a little research and report back :)