Thanks for the interest on the flink-kubernetes-operator project. I believe you could leave a comment in the ticket FLINK-27049. If the reporter has not start working on this ticket, then you could be assigned.
Best, Yang Hao t Chang <htch...@us.ibm.com> 于2022年4月6日周三 06:30写道： > Hi Gyula > > > > Thanks for the reply. I look forward to making contributions. I am > assuming if an issue, for example this one > <https://issues.apache.org/jira/browse/FLINK-27049?jql=project%20%3D%20FLINK%20AND%20component%20%3D%20%22Kubernetes%20Operator%22%20AND%20status%3DOpen%20>, > has no assignee, then it’s probably a good candidate to work on? > > > > *From: *Gyula Fóra <gyf...@apache.org> > *Date: *Saturday, April 2, 2022 at 2:19 AM > *To: *Hao t Chang <htch...@us.ibm.com> > *Cc: *"user@flink.apache.org" <user@flink.apache.org> > *Subject: *[EXTERNAL] Re: The flink-kubernetes-operator vs third party > flink operators > > > > 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 ZjQcmQRYFpfptBannerStart > > This Message Is From an External Sender > > This message came from outside your organization. > > ZjQcmQRYFpfptBannerEnd > > 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 > >
