nee, then it’s probably a good candidate to work on?
>
>
>
> *From: *Gyula Fóra
> *Date: *Saturday, April 2, 2022 at 2:19 AM
> *To: *Hao t Chang
> *Cc: *"user@flink.apache.org"
> *Subject: *[EXTERNAL] Re: The flink-kubernetes-operator vs third party
> f
signee, then it’s probably a good candidate to work on?
From: Gyula Fóra
Date: Saturday, April 2, 2022 at 2:19 AM
To: Hao t Chang
Cc: "user@flink.apache.org"
Subject: [EXTERNAL] Re: The flink-kubernetes-operator vs third party flink
operators
Hi! The main difference at the moment is
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 Golan
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
k
