Re: What is the flink-kubernetes-operator webhook for?

Okay, thank you both. We will disable webhook creation unless we end up needing it. On Fri, Dec 9, 2022 at 9:39 AM Gyula Fóra wrote: > To add to what Matyas said: > > Validation in itself is a mandatory step for every spec change that is > submitted to guard against broken configs (things

Re: 关于Flink重启策略疑惑

你好 1.Flink中(JM)JobMaster会监控各个Task的状态，如果Task由于某些原因失败了，JM触发failover,并且决策哪些task应该被重新启动。当然，如果JM挂掉的话，Flink支持配置高可用(HA),通过持久化一些信息到外部系统，从而做到通过standby JM正确接管作业。 2.无论单个Task挂掉还是TaskManager挂掉failover流程都可以正确处理，处理流程基本是一致的，TaskManager挂掉可以认为是上面所有被调度上去的Task fail了。 Best regards, Weijie 李义 于2022年12月9日周五

Re: What is the flink-kubernetes-operator webhook for?

To add to what Matyas said: Validation in itself is a mandatory step for every spec change that is submitted to guard against broken configs (things like negative parallelism etc). But validation can happen in 2 places. It can be done through the webhook, which would result in upfront rejection

Re: What is the flink-kubernetes-operator webhook for?

Hi Otto, webhooks in general are optional components of the k8s operator pattern. Mostly used for validation, sometimes for changing custom resources and handling multiple versions, etc. It's an optional component in the Flink Kubernetes Operator too. Regards, Matyas On Fri, Dec 9, 2022 at 5:59

What is the flink-kubernetes-operator webhook for?

Hello! What is the Flink Kubernetes Webhook for? I probably don't know just because I don't know k8s that well, but reading code and other docs didn't particular enlighten me :)

Re: Could not restore keyed state backend for KeyedProcessOperator

Lifecycle rulesNone On Fri, Dec 9, 2022 at 3:17 AM Hangxiang Yu wrote: > Hi, Lars. > Could you check whether you have configured the lifecycle of google cloud > storage[1] which is not recommended in the flink checkpoint usage? > > [1] https://cloud.google.com/storage/docs/lifecycle > > On Fri,

Re: ArgoCD unable to process health from k8s FlinkDeployment - stuck in Processing

Hi! The resource lifecycle state is currently not shown explicitly in the status. You are confusing it with reconciliation status. At the moment you can only get this through the Java client:

ArgoCD unable to process health from k8s FlinkDeployment - stuck in Processing

Morning all, Recently been testing the Flink k8s operator (flink.apache.org/v1beta1) and although the jobs do startup and run perfectly fine, their status in ArgoCD is not yet as it should be, some details: When describing the flinkdeployment I'm currently trying to test, the follows appears in

Re: ZLIB Vulnerability Exposure in Flink statebackend RocksDB

Hi Vidya, Please keep in mind that the Flink project is driven by volunteers. If you're noticing an outdated version for the lz4 compression library and an update is required, it would be great if you can open the PR to update that dependency yourself. Best regards, Martijn On Thu, Dec 8, 2022