Re: standalone mode support in the kubernetes operator (FLIP-25)

I think at least we have the following advantages(in some cases). * We do not need to configure a service account for JobManager, which allows it could allocate/delete pods from Kubernetes APIServer. * The reactive mode[1] could only work with standalone cluster. [1]. https://nightlies.apache.org/

Re: standalone mode support in the kubernetes operator (FLIP-25)

Hi all, Does 'standalone mode support in the kubernetes operator' means: Using flink-k8s-operator to manage jobs deployed in a standalone cluster? What is the advantag doing so. Yang Wang 于2022年7月14日周四 10:55写道： > > I think the standalone mode support is expected to be done in the version > 1.2.0

Re: standalone mode support in the kubernetes operator (FLIP-25)

I think the standalone mode support is expected to be done in the version 1.2.0[1], which will be released on Oct 1 (ETA). [1]. https://cwiki.apache.org/confluence/display/FLINK/Release+Schedule+and+Planning Best, Yang Javier Vegas 于2022年7月14日周四 06:25写道： > Hello! The operator docs > https://n

standalone mode support in the kubernetes operator (FLIP-25)

Hello! The operator docs https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/docs/concepts/overview/ say "The Operator does not support Standalone Kubernetes deployme