Hi! Thank you for your interest in contributing to the operator.
The operator persists information in the status of the FlinkDeployment resource. We should not need any additional persistence layer on top of this in the current design. Could you please give me a concrete example of what is not working with the current design? Thanks, Gyula On Sat, Feb 19, 2022 at 7:06 AM zhengyu chen <jam.gz...@gmail.com> wrote: > Hi, regarding the construction of k8s Flink Operator, I have already > completed some functions. I hope to contribute this part of the functions > and discuss with the community how to improve it. How should I start? > > So far I have seen that the component has no operation persistence. Should > we persist its operation? for example, when I have a SessionCluster > deployment, I need to write its metadata to an external storage system in > yaml mode, > such as use mysql for storage. This design idea is similar to etcd in > k8s.If our k8s Flink Operator application is restarted, We can recover > metadata information about deployment jobs, clusters, and so on based on > the database > > Best > ConradJam > > On 2022/01/25 05:08:01 Thomas Weise wrote: > > Hi, > > > > As promised in [1] we would like to start the discussion on the > > addition of a Kubernetes operator to the Flink project as FLIP-212: > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-212%3A+Introduce+Flink+Kubernetes+Operator > > > > Please note that the FLIP is currently focussed on the overall > > direction; the intention is to fill in more details once we converge > > on the high level plan. > > > > Thanks and looking forward to a lively discussion! > > > > Thomas > > > > [1] https://lists.apache.org/thread/l1dkp8v4bhlcyb4tdts99g7w4wdglfy4 > > >
