You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2026/07/14 20:09:00 UTC
[jira] [Closed] (FLINK-40092) BlueGreen transition should finalize immediately after deleting previous deployment
[ https://issues.apache.org/jira/browse/FLINK-40092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gyula Fora closed FLINK-40092.
------------------------------
Fix Version/s: kubernetes-operator-1.16.0
Resolution: Fixed
merged to main 567ac1cca7987df19308e519715aca0fe71f4005
> BlueGreen transition should finalize immediately after deleting previous deployment
> -----------------------------------------------------------------------------------
>
> Key: FLINK-40092
> URL: https://issues.apache.org/jira/browse/FLINK-40092
> Project: Flink
> Issue Type: Bug
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.15.0
> Reporter: Calico Shop
> Priority: Major
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.16.0
>
>
> During a BlueGreen deployment transition, once the previous FlinkDeployment is successfully deleted, the operator currently waits for another reconciliation loop before finalizing the FlinkBlueGreenDeployment into the next ACTIVE_* state.
> This extra reconciliation is unnecessary because the old deployment has already been removed and the transition can be finalized immediately. The operator should call the existing finalization logic in the same reconciliation that successfully deletes the previous deployment, while preserving retry behavior when deletion is not acknowledged.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)