search

GoogleCloudPlatform / flink-on-k8s-operator

[DEPRECATED] Kubernetes operator for managing the lifecycle of Apache Flink and Beam applications.
Apache License 2.0
659 stars 265 forks source link

Not Able to trigger a new deployment when image pull failed or job failed #426

Open yanghui16355 opened 3 years ago

yanghui16355 commented 3 years ago

There is an issue for operator that it is not able to trigger a new deployment when image pull failed or job failed.

More specifically, when I make a deployment with wrong image or job got an exception, the flink cluster created but job is not able to run which is expected. I want to fix it by making a new deployment with correct image, however, the operator is not able to trigger a new deployment and old flink cluster keep with wrong status.

Any reason why the operator skip the deployment for this situation? Should we have a option to force trigger the new deployment by user no matter what status for the current flink cluster?

@functicons please help check the issue, thanks!

yanghui16355 commented 3 years ago

@functicons any comment for my issue, thanks!