Re: [DISCUSS] FLIP-223: Implement standalone mode support in the kubernetes operator

I think Usamah is working right now towards a first prototype PR of the standalone implementation. We should wait for that before we start splitting the work :) Gyula On Thu, Jun 23, 2022 at 3:25 PM zhengyu chen wrote: > I only see LAST_STATE support for zookeeper here（FLINK-27416 >

RE: [DISCUSS] FLIP-223: Implement standalone mode support in the kubernetes operator

I only see LAST_STATE support for zookeeper here（FLINK-27416 ）, but I don't see anything about k8s. What do you think about this? I am very willing to move this work forward -- Best ConradJam

Re: [DISCUSS] FLIP-223: Implement standalone mode support in the kubernetes operator

+1 for the proposal :) I think this will fit nicely with the current API. If we use deployments we could simply extend the current status interfaces with taskManagerDeploymentStatus (we already have jobManagerDeploymentStatus) for the standalone mode. We would have to check how we could use the

Re: [DISCUSS] FLIP-223: Implement standalone mode support in the kubernetes operator

Thanks for the feedback. # The TaskManager replicas Yeah I think this makes sense and explicitly stating TM replicas makes more sense in the standalone mode. I will update the FLIP and clarify this. # How the JobManager and TaskManager pods are managed? I think deployments for both TaskManager

Re: [DISCUSS] FLIP-223: Implement standalone mode support in the kubernetes operator

Thanks for creating the FLIP-223 and starting the discussion. I have some quick questions. # The TaskManager replicas The TaskManager replicas need to be configured both for standalone session and application. Because it could not be calculated if the parallelism is set via java codes. # How

[DISCUSS] FLIP-223: Implement standalone mode support in the kubernetes operator

Hi everyone, We would like to start the discussion of the adding standalone mode support to the Flink Kubernetes operator. Standalone mode was initially considered as part of FLIP-212 but decided to be out of scope to focus on Flink native k8s integration for that FLIP [1]. Standalone support w