Hi Svend, thank you so much to sharing your experience! GCP k8s operator looks promising (currently i’m trying to build it and run helm chart. An issue <https://github.com/GoogleCloudPlatform/flink-on-k8s-operator/issues/266> with k8s version 1.18+ is road block right now, but I see that there is a solution), and also seems like flink team also refers <http://disq.us/p/2f7goq6> to it this implementation.
In your setup did you solve the problem of visualising list of in-progress jobs? > One worrying point though is that the maintainers of the repo seem to have > become silent in March this year. lyfts implementation <https://github.com/lyft/flinkk8soperator> (haven’t tried it yet) seems to be even more abandoned (last release 20/04/2020). > 29 мая 2021 г., в 11:23, Svend <stream...@svend.xyz> написал(а): > > Hi Ilya, > > At my company we're currently using the GCP k8s operator (2nd on your list). > Our usage is very moderate, but so far it works great for us. > > We appreciate that when upgrading the application, it triggers automatically > a savepoint during shutdown and resumes from it when restarting. It also > allows to take savepoints at regular intervals (we take one per day > currently). > > We're using it with Flink 1.12.4 and AWS EKS. > > Getting the Flink metrics and logs exported to our monitoring system worked > out of the box. > > Configuring IAM roles and K8s service account for saving checkpoints and > savepoints to S3 required a bit more fiddling although we got it working. > > Happy to share code snippet about any of that if that's useful :) > > It was last updated with Flink 1.11 in mind, so there is currently no > built-in support for the reactive scaling mode recently added in Flink 1.13. > > One worrying point though is that the maintainers of the repo seem to have > become silent in March this year. There is a small and active community > around it though and issues and PRs keep on arriving and are waiting for > feed-back. It's all free and OSS, so who are we to complain? Though it's > still an important attention point. > > Hope this helps, > > Svend > > > > > > On Fri, 28 May 2021, at 9:09 AM, Ilya Karpov wrote: >> Hi there, >> >> I’m making a little research about the easiest way to deploy link job to k8s >> cluster and manage its lifecycle by k8s operator. The list of solutions is >> below: >> - https://github.com/fintechstudios/ververica-platform-k8s-operator >> <https://github.com/fintechstudios/ververica-platform-k8s-operator> >> - https://github.com/GoogleCloudPlatform/flink-on-k8s-operator >> <https://github.com/GoogleCloudPlatform/flink-on-k8s-operator> >> - https://kudo.dev/docs/examples/apache-flink.html >> <https://kudo.dev/docs/examples/apache-flink.html> >> - https://github.com/wangyang0918/flink-native-k8s-operator >> <https://github.com/wangyang0918/flink-native-k8s-operator> >> >> If you are using smth that is not listed above please share! Any share about >> how specific solution works is greatly appreciated. >> >> Thanks in advance
