search

GoogleCloudPlatform / flink-on-k8s-operator

[DEPRECATED] Kubernetes operator for managing the lifecycle of Apache Flink and Beam applications.
Apache License 2.0
658 stars 266 forks source link

Check project status #446

Open becoming-proc opened 3 years ago

becoming-proc commented 3 years ago

Is this repository still maintained and ongoing project? I want to utilize this project, but it seems that there is no recent activity, so I want to check it. If it's difficult to be maintained by GCP, how about to open up some of the review authority to community members? Or, if possible, how about donating to an open source foundation, like in the case of the airflow operator? (https://github.com/GoogleCloudPlatform/airflow-operator/issues/103) There are still a lot of community activities, so I hope this project continues smoothly.

becoming-proc commented 3 years ago

cc Google folks @functicons @hongyegong @medb @cdibona

shashken commented 3 years ago

I suggested starting with more reviewers and a working slack channel at #441 There is activity here, but the PRs are not getting reviewed and the issues are not closed. Its up to the google folks to decide, but something needs to be done here. If anyone reading this has a way of contacting one of the maintainers, please ask them to take a look.

mvbakker commented 3 years ago

@becoming-proc, we are working with and developing for this operator, so it's ongoing if you'd ask me. However, as @shashken pointed out, PRs and issues seem to be a bit stuck at the moment.

sv3ndk commented 3 years ago

We're also working with this operator, which so far seems to work pretty well for us. I sent a minor PR as well already which like others pointed out above has not yet been merged. We'd be happy to send more contributions although indeed the lack of response is worrying.

andre-taveira commented 3 years ago

Same here ! The project is super cool and we're using in prod ! Definitely opening up for more reviewers and getting a working slack channel would be great :)

jlewi commented 2 years ago

The code is Apache License so I don't think there's anything blocking creation of a fork to continue development. However, that doesn't really address the question about whether Google is still investing in this. Judging from the activity on this issue and repo the answer appears to be no.

Maybe @ververica be interested in incubating this project further?

elanv commented 2 years ago

They have a similar commercial product, so I wonder if they will be interested.

Apparently, there are a lot of forked repositories and individual activities. However, I am concerned that there is already a lot of fragmentation going on.

I think it's a good time to look for ways to cooperate if anyone is interested. For example, we can create a new repository or join as reviewers in a particular repository to cooperate.

Do you have any good ideas or suggestions?

sv3ndk commented 2 years ago

Hi everyone,

I've been through all the forks this morning, most of them are inactive, although about 5 have received some regular commits since February this year. Out of them, https://github.com/spotify/flink-on-k8s-operator seems the most actively maintained to me, even though it's mostly a one person effort so far.

I reached out to the owner and he confirms he plan on working on this and would welcome PR: https://github.com/spotify/flink-on-k8s-operator/issues/82

I'm going to rebase and submit my modest PR to his repo sometime this week. I humbly suggest we all do the same, this repo might be a nice place to get the effort going.

What do you think?