You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Daniel Rossos (Jira)" <ji...@apache.org> on 2026/01/14 15:20:00 UTC
[jira] [Created] (FLINK-38915) Suspending Pipeline Breaks FlinkBlueGreenDeployment
Daniel Rossos created FLINK-38915:
-------------------------------------
Summary: Suspending Pipeline Breaks FlinkBlueGreenDeployment
Key: FLINK-38915
URL: https://issues.apache.org/jira/browse/FLINK-38915
Project: Flink
Issue Type: Improvement
Components: Kubernetes Operator
Reporter: Daniel Rossos
*Current Behaviour*
Setting "spec.template.spec.job.state" to "suspended" in FlinkBlueGreenDeployment triggers a broken transition. The controller triggers a blue-green transition that creates a new suspended deployment which then fails because the new 'green' pipeline never reaches running state. This creates a broken transition.
*Proposed Solution*
The BlueGreen deployment should properly handle these transitions to "suspension state". The proposed method (as discussed in discussion thread [here|https://lists.apache.org/thread/0hhct3ktws3wv9psrgyro0kdy8g1hjnq]) is as follows:
State changes to "spec.template.spec.job.state" trigger in-place suspension of the active child. While suspended, all blue-green transitions are ignored until spec is set back to running. Once running again, spins up new deployment with any accumulated spec changes and resumes normal blue-green operations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)