You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "James Kan (Jira)" <ji...@apache.org> on 2026/01/05 23:24:00 UTC
[jira] [Created] (FLINK-38867) FlinkBlueGreenDeployment: savepointRedeployNonce does not respect user-provided initialSavepointPath
James Kan created FLINK-38867:
---------------------------------
Summary: FlinkBlueGreenDeployment: savepointRedeployNonce does not respect user-provided initialSavepointPath
Key: FLINK-38867
URL: https://issues.apache.org/jira/browse/FLINK-38867
Project: Flink
Issue Type: Bug
Components: Kubernetes Operator
Reporter: James Kan
h4. Description
The FlinkBlueGreenDeployment controller does not properly honor the [`savepointRedeployNonce`|https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/docs/custom-resource/job-management/#redeploy-using-the-savepointredeploynonce] parameter during subsequent deployments. When the nonce is incremented, the controller ignores the user-specified `initialSavepointPath` and instead uses the savepoint from the previous deployment (blue or green) being terminated.
h4. Expected Behavior
When `savepointRedeployNonce` is incremented in the FlinkBlueGreenDeployment spec, the controller should respect the user-specified `initialSavepointPath` and ensure the new active deployment (blue or green being transitioned to) starts from the specified savepoint location.
h4. Current Behavior
- Initial deployments: `initialSavepointPath` is correctly applied ✓
- Subsequent deployments for FlinkBlueGreenDeployments: `initialSavepointPath` is ignored when `savepointRedeployNonce` is updated ✗.
h4. Impact
This prevents manual savepoint selection functionality required for manual recoveries and creates inconsistencies with the expected behaviour of savepointRedeployNonce described in the Flink documentation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)