drossos opened a new pull request, #1051:
URL: https://github.com/apache/flink-kubernetes-operator/pull/1051
## What is the purpose of the change
This pull request fixes a bug where FlinkBlueGreenDeployment ignores the
user-specified initialSavepointPath when savepointRedeployNonce is incremented.
The controller now properly honors savepointRedeployNonce changes and uses the
specified savepoint location for redeployment, aligning Blue/Green deployment
behavior with standard FlinkDeployment behavior.
## Brief change log
- Added BlueGreenDiffType.SAVEPOINT_REDEPLOY to handle nonce-triggered
redeployments
- Updated FlinkBlueGreenDeploymentSpecDiff to detect and prioritize
savepointRedeployNonce changes
- Added startSavepointRedeployTransition() to skip savepoint triggering and
use initialSavepointPath from spec
## Verifying this change
- Added
`verifySavepointRedeployNonceTriggersTransitionWithInitialSavepointPath`
integration test in `FlinkBlueGreenDeploymentControllerTest` that verifies the
full savepoint redeploy flow:
- Deploys to stable `ACTIVE_BLUE` state
- Bumps `savepointRedeployNonce` with user-specified `initialSavepointPath`
- Verifies controller skips savepoint triggering and transitions directly
to `TRANSITIONING_TO_GREEN`
- Verifies Green deployment uses the user-specified `initialSavepointPath`
- Verifies successful completion to `ACTIVE_GREEN`
- Updated existing tests and expanded existing tests to reflect new behavior
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): no
- The public API, i.e., is any changes to the `CustomResourceDescriptors`: no
- Core observer or reconciler logic that is regularly executed: yes
## Documentation
- Does this pull request introduce a new feature? no (bug fix)
- If yes, how is the feature documented? not applicable (fixes existing
documented feature)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
