[jira] [Created] (FLINK-33222) Operator rollback app when it should not

["Nicolas Fraison (Jira)" <ji...@apache.org>]

Nicolas Fraison created FLINK-33222:
---------------------------------------

             Summary: Operator rollback app when it should not
                 Key: FLINK-33222
                 URL: https://issues.apache.org/jira/browse/FLINK-33222
             Project: Flink
          Issue Type: Bug
          Components: Kubernetes Operator
         Environment: Flink operator 1.6 - Flink 1.17.1
            Reporter: Nicolas Fraison


The operator can decide to rollback when an update of the job spec is performed on 
savepointTriggerNonce or initialSavepointPath if the app has been deployed since more than KubernetesOperatorConfigOptions.DEPLOYMENT_READINESS_TIMEOUT.
 
This is due to the objectmeta generation being [updated|https://github.com/apache/flink-kubernetes-operator/blob/release-1.6/flink-kubernetes-operator/src/main/java/org/apache/flink/kubernetes/operator/reconciler/deployment/AbstractFlinkResourceReconciler.java#L169] when changing those spec and leading to the lastReconcileSpec not being aligned with the stableReconcileSpec while those spec are well ignored when checking for upgrade diff
 
Looking at the main branch we should still face the same issue as the same [update|https://github.com/apache/flink-kubernetes-operator/blob/main/flink-kubernetes-operator/src/main/java/org/apache/flink/kubernetes/operator/reconciler/deployment/AbstractFlinkResourceReconciler.java#L169] is performed at the end of the reconcile loop



--
This message was sent by Atlassian Jira
(v8.20.10#820010)