Hi Melin. Flink integration with Kubernetes is really just about resource provisioning. The behavior that you describe is caused by Flink’s resilience feature, implemented as Job restart policy. And it would be similar even without K8s integration. If the job is configured to restart on errors, it will do so.
You can control this behavior by specifying the desired job restart strategy and configuring it to your preference. For instance, you could configure exponential back-off with 3 attempts. See: https://nightlies.apache.org/flink/flink-docs-release-1.13/docs/dev/execution/task_failure_recovery/ Nix. From: melin li <libinsong1...@gmail.com> Date: Monday, May 12, 2025 at 7:43 AM To: user@flink.apache.org <user@flink.apache.org> Subject: flink on native kubernetes does not rely on deployment to start Pod Hello, flink on native kubernetes starts the task. If the pod fails, the pod will keep trying to restart. Especially the batch mode. I don't want to keep restarting. flink on native kubernetes starts Pods directly. Is this design more reasonable?
