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/flink/flink-docs-release-1.15/docs/deployment/elastic_scaling/#reactive-mode Best, Yang yidan zhao <hinobl...@gmail.com> 于2022年7月15日周五 10:13写道： > 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 <danrtsey...@gmail.com> 于2022年7月14日周四 10:55写道： > > > > 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 <jve...@strava.com> 于2022年7月14日周四 06: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 deployments yet" > and mentions > https://cwiki.apache.org/confluence/display/FLINK/FLIP-225%3A+Implement+standalone+mode+support+in+the+kubernetes+operator > as a "what's next" step. Is there a timeline for that to be released? > >> > >> Thanks, > >> > >> Javier Vegas >
