morhidi commented on code in PR #271:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/271#discussion_r901600207
##########
flink-kubernetes-operator/src/main/java/org/apache/flink/kubernetes/operator/observer/deployment/AbstractDeploymentObserver.java:
##########
@@ -252,6 +257,60 @@ private void onMissingDeployment(FlinkDeployment
deployment) {
EventUtils.Component.JobManagerDeployment);
}
+ /**
+ * Checks a deployment that is currently in the UPGRADING state whether it
was already deployed
+ * but we simply miss the status information. After comparing the target
resource generation
+ * with the one from the possible deployment if they match we update the
status to the already
+ * DEPLOYED state.
+ *
+ * @param flinkDep Flink resource to check.
+ * @param context Context for reconciliation.
+ */
+ private void checkIfAlreadyUpgraded(FlinkDeployment flinkDep, Context
context) {
Review Comment:
The way I understand the method catches up with initial deployments too, and
the UPGRADING state covers both status. Distinguishing two states DEPLOYING and
UPGRADING makes sense to me, or calling the method
`checkIfAlreadyDeployedOrUpgraded`. But maybe I don't clearly understand the
logic here.
--
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: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
