Hi Bhaskar, IIUC, flink-k8s-operator and Flink native K8s mode are orthogonal. They do not mean to replace other one.
The flink-k8s-operator is more like a Flink lifecycle management tool. It could make deploying a Flink application on K8s easier. We just need to apply a CR yaml and is more friendly to K8s users. The flink-k8s-operator could integrate with standalone mode[1], but also native K8s mode[2]. [1]. https://github.com/GoogleCloudPlatform/flink-on-k8s-operator [2]. https://github.com/wangyang0918/flink-native-k8s-operator Best, Yang Vijay Bhaskar <bhaskar.eba...@gmail.com> 于2021年10月22日周五 下午1:59写道： > Understood that we have kubernetes HA configuration where we specify s3:// > or HDFS:/// persistent storage, as mentioned here: > https://ci.apache.org/projects/flink/flink-docs-master/docs/deployment/ha/kubernetes_ha/ > > Regards > Bhaskar > > On Fri, Oct 22, 2021 at 10:47 AM Vijay Bhaskar <bhaskar.eba...@gmail.com> > wrote: > >> All, >> I have used flink upto last year using flank 1.9. That time we built our >> own cluster using zookeeper and monitoring jobs. Now I am revisiting >> different applications. Found that community has come up with this native >> kubernetes deployment: >> >> https://ci.apache.org/projects/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/#application-mode >> >> Now i am getting question: >> >> Why do we need second thought, we can directly deploy in native >> kubernetes in Application Mode? >> >> Only thing is if I add little monitoring from outside that suffice right? >> >> I believe this has eliminated the need for >> 1. Kubernetes Operator in flink ( Provided adding monitoring using flink >> logs, on top) >> 2. Zookeeper usage and cluster mode.. >> >> Where is the state stored now? Is it stored in /etcd in kubernetes? >> >> Regards >> Bhaskar >> >> >> >> >>
