[
https://issues.apache.org/jira/browse/FLINK-26892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513971#comment-17513971
]
Biao Geng commented on FLINK-26892:
-----------------------------------
I try to summary what we should do for this case:
1. Save latest validated config ({{lastReconciledSpec}} should have already
been sufficient.)
2. Adjust current logic to observe with latest validated config -> validate new
config -> reconcile with new config
Is there any drawback of above idea? If it is fine, I can take this ticket and
work on it.
> Observe current status before validating CR changes
> ---------------------------------------------------
>
> Key: FLINK-26892
> URL: https://issues.apache.org/jira/browse/FLINK-26892
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Reporter: Gyula Fora
> Priority: Major
> Fix For: kubernetes-operator-1.0.0
>
>
> Currently validation is the first step in the controller loop which means
> that when there is a validation error we fail to observe the status of
> currently running deployments.
> We should change the order of operations and observe before validation.
> Furthermore observe should use the previous configuration not the one after
> the CR change.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
