Hi! The main difference at the moment is the programming language and the APIs used to interact with Flink.
The flink-kubernetes-operator, uses Java and interacts with Flink using the built in (native) clients. The other operators have been around since earlier Flink versions. They all use Golang, and some of them have been already abandoned by the initial developers. In many cases they also do not support the latest Flink operational features. With the flink-kubernetes-operator project we aimed to take inspiration from the existing operators and create a project where Flink developers can easily contribute and could be maintained together with Flink itself while keeping up the high quality standards. We hope that developers of the other operators would start contributing soon :) Cheers, Gyula On Sat, 2 Apr 2022 at 11:01, Hao t Chang <htch...@us.ibm.com> wrote: > Hi > > > > I started looking into Flink recently more specifically the > flink-kubernetes-operator so I only know little about it. I found at least > 3 other Flink K8s operators that Lyft, Google, and Spotify developed. > Could someone please enlighten me what is the difference of these third > party Flink k8s operators ? and why don’t these parties contribute to the > same repo in the Flink community from the beginning ? Thanks. > > > > Ted >
